Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - Linux カーネルにおいて、以下の脆弱性は解決されました： bpf: Fix UAF due to race between btf_try_get_module and load_module While working on code to populate kfunc BTF ID sets for module BTF from its initcall, I noticed that by the time the initcall is invoked, the module BTF can already be seen by userspace (and the BPF verifier). The existing btf_try_get_module calls try_module_get which only fails if mod->state == MODULE_STATE_GOING, i.e. it can increment module reference when module initcall is happening in parallel. Currently, BTF parsing happens from MODULE_STATE_COMING notifier callback. At this point, the module initcalls have not been invoked. The notifier callback parses and prepares the module BTF, allocates an ID, which publishes it to userspace, and then adds it to the btf_modules list allowing the kernel to invoke btf_try_get_module for the BTF. However, at this point, the module has not been fully initialized (i.e. its initcalls have not finished). The code in module.c can still fail and free the module, without caring for other users. However, nothing stops btf_try_get_module from succeeding between the state transition from MODULE_STATE_COMING to MODULE_STATE_LIVE. This leads to a use-after-free issue when BPF program loads successfully in the state transition, load_module's do_init_module call fails and frees the module, and BPF program fd on close calls module_put for the freed module. Future patch has test case to verify we don't regress in this area in future. There are multiple points after prepare_coming_module (in load_module) where failure can occur and module loading can return error. We illustrate and test for the race using the last point where it can practically occur (in module __init function). An illustration of the race: CPU 0 CPU 1 load_module notifier_call(MODULE_STATE_COMING) btf_parse_module btf_alloc_id // Published to userspace list_add(&btf_mod->list, btf_modules) mod->init(...) ... ^ bpf_check | check_pseudo_btf_id | btf_try_get_module | returns true | ... ... | module __init in progress return prog_fd | ... ... V if (ret < 0) free_module(mod) ... close(prog_fd) ...
    bpf_prog_free_deferred module_put(used_btf.mod) // use-after-free We fix this issue by setting a flag BTF_MODULE_F_LIVE, from the notifier callback when MODULE_STATE_LIVE state is reached for the module, so that we return NULL from btf_try_get_module for modules that are not fully formed. Since try_module_get already checks that module is not in MODULE_STATE_GOING state, and that is the only transition a live module can make before being removed from btf_modules list, this is enough to close the race and prevent the bug. A later selftest patch crafts the race condition artifically to verify that it has been fixed, and that verifier fails to load program (with ENXIO). Lastly, a couple of comments: 1. Even if this race didn't exist, it seems more appropriate to only access resources (ksyms and kfuncs) of a fully formed module which has been initialized completely. 2. This patch was born out of need for synchronization against module initcall for the next patch, so it is needed for correctness even without the aforementioned race condition. The BTF resources initialized by module initcall are set up once and then only looked up, so just waiting until the initcall has finished ensures correct behavior. (CVE-2022-49236)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 在 Linux 内核中，已解决以下漏洞： bpf: Fix UAF due to race between btf_try_get_module and load_module While working on code to populate kfunc BTF ID sets for module BTF from its initcall, I noticed that by the time the initcall is invoked, the module BTF can already be seen by userspace (and the BPF verifier). The existing btf_try_get_module calls try_module_get which only fails if mod->state == MODULE_STATE_GOING, i.e. it can increment module reference when module initcall is happening in parallel. Currently, BTF parsing happens from MODULE_STATE_COMING notifier callback. At this point, the module initcalls have not been invoked. The notifier callback parses and prepares the module BTF, allocates an ID, which publishes it to userspace, and then adds it to the btf_modules list allowing the kernel to invoke btf_try_get_module for the BTF. However, at this point, the module has not been fully initialized (i.e. its initcalls have not finished). The code in module.c can still fail and free the module, without caring for other users. However, nothing stops btf_try_get_module from succeeding between the state transition from MODULE_STATE_COMING to MODULE_STATE_LIVE. This leads to a use-after-free issue when BPF program loads successfully in the state transition, load_module's do_init_module call fails and frees the module, and BPF program fd on close calls module_put for the freed module. Future patch has test case to verify we don't regress in this area in future. There are multiple points after prepare_coming_module (in load_module) where failure can occur and module loading can return error. We illustrate and test for the race using the last point where it can practically occur (in module __init function). An illustration of the race: CPU 0 CPU 1 load_module notifier_call(MODULE_STATE_COMING) btf_parse_module btf_alloc_id // Published to userspace list_add(&btf_mod->list, btf_modules) mod->init(...) ... ^ bpf_check | check_pseudo_btf_id | btf_try_get_module | returns true | ... ... | module __init in progress return prog_fd | ... ... V if (ret < 0) free_module(mod) ... close(prog_fd) ...
    bpf_prog_free_deferred module_put(used_btf.mod) // use-after-free We fix this issue by setting a flag BTF_MODULE_F_LIVE, from the notifier callback when MODULE_STATE_LIVE state is reached for the module, so that we return NULL from btf_try_get_module for modules that are not fully formed. Since try_module_get already checks that module is not in MODULE_STATE_GOING state, and that is the only transition a live module can make before being removed from btf_modules list, this is enough to close the race and prevent the bug. A later selftest patch crafts the race condition artifically to verify that it has been fixed, and that verifier fails to load program (with ENXIO). Lastly, a couple of comments: 1. Even if this race didn't exist, it seems more appropriate to only access resources (ksyms and kfuncs) of a fully formed module which has been initialized completely. 2. This patch was born out of need for synchronization against module initcall for the next patch, so it is needed for correctness even without the aforementioned race condition. The BTF resources initialized by module initcall are set up once and then only looked up, so just waiting until the initcall has finished ensures correct behavior. (CVE-2022-49236)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - 在 Linux 核心中，已解決下列弱點： bpf: Fix UAF due to race between btf_try_get_module and load_module While working on code to populate kfunc BTF ID sets for module BTF from its initcall, I noticed that by the time the initcall is invoked, the module BTF can already be seen by userspace (and the BPF verifier). The existing btf_try_get_module calls try_module_get which only fails if mod->state == MODULE_STATE_GOING, i.e. it can increment module reference when module initcall is happening in parallel. Currently, BTF parsing happens from MODULE_STATE_COMING notifier callback. At this point, the module initcalls have not been invoked. The notifier callback parses and prepares the module BTF, allocates an ID, which publishes it to userspace, and then adds it to the btf_modules list allowing the kernel to invoke btf_try_get_module for the BTF. However, at this point, the module has not been fully initialized (i.e. its initcalls have not finished). The code in module.c can still fail and free the module, without caring for other users. However, nothing stops btf_try_get_module from succeeding between the state transition from MODULE_STATE_COMING to MODULE_STATE_LIVE. This leads to a use-after-free issue when BPF program loads successfully in the state transition, load_module's do_init_module call fails and frees the module, and BPF program fd on close calls module_put for the freed module. Future patch has test case to verify we don't regress in this area in future. There are multiple points after prepare_coming_module (in load_module) where failure can occur and module loading can return error. We illustrate and test for the race using the last point where it can practically occur (in module __init function). An illustration of the race: CPU 0 CPU 1 load_module notifier_call(MODULE_STATE_COMING) btf_parse_module btf_alloc_id // Published to userspace list_add(&btf_mod->list, btf_modules) mod->init(...) ... ^ bpf_check | check_pseudo_btf_id | btf_try_get_module | returns true | ... ... | module __init in progress return prog_fd | ... ... V if (ret < 0) free_module(mod) ... close(prog_fd) ...
    bpf_prog_free_deferred module_put(used_btf.mod) // use-after-free We fix this issue by setting a flag BTF_MODULE_F_LIVE, from the notifier callback when MODULE_STATE_LIVE state is reached for the module, so that we return NULL from btf_try_get_module for modules that are not fully formed. Since try_module_get already checks that module is not in MODULE_STATE_GOING state, and that is the only transition a live module can make before being removed from btf_modules list, this is enough to close the race and prevent the bug. A later selftest patch crafts the race condition artifically to verify that it has been fixed, and that verifier fails to load program (with ENXIO). Lastly, a couple of comments: 1. Even if this race didn't exist, it seems more appropriate to only access resources (ksyms and kfuncs) of a fully formed module which has been initialized completely. 2. This patch was born out of need for synchronization against module initcall for the next patch, so it is needed for correctness even without the aforementioned race condition. The BTF resources initialized by module initcall are set up once and then only looked up, so just waiting until the initcall has finished ensures correct behavior. (CVE-2022-49236)

請注意，Nessus 依賴供應商報告的套件存在。

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    ipv4: Fix a data-race around sysctl_fib_sync_mem.(CVE-2022-49637)

    ima: Fix potential memory leak in ima_init_crypto().(CVE-2022-49627)

    MIPS: pgalloc: fix memory leak caused by pgd_free().(CVE-2022-49210)

    ip: Fix data-races around sysctl_ip_fwd_use_pmtu.(CVE-2022-49604)

    net: tipc: fix possible refcount leak in tipc_sk_create()(CVE-2022-49620)

    bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full(CVE-2022-49209)

    net: remove two BUG() from skb_checksum_help().(CVE-2022-49497)

    usbnet: fix memory leak in error case(CVE-2022-49657)

    ip: Fix a data-race around sysctl_ip_autobind_reuse.(CVE-2022-49600)

    cipso: Fix data-races around sysctl.(CVE-2022-49639)

    nexthop: Fix data-races around nexthop_compat_mode.(CVE-2022-49629)

    tracing/histograms: Fix memory leak problem(CVE-2022-49648)

    SUNRPC: Fix the svc_deferred_event trace class(CVE-2022-49065)

    af_unix: Fix a data-race in unix_dgram_peer_wake_me().(CVE-2022-49344)

    RDMA/cm: Fix memory leak in ib_cm_insert_listen(CVE-2022-49671)

    ip: Fix a data-race around sysctl_fwmark_reflect.(CVE-2022-49602)

    raw: Fix a data-race around sysctl_raw_l3mdev_accept.(CVE-2022-49631)

    icmp: Fix data-races around sysctl.(CVE-2022-49638)

    tty: synclink_gt: Fix null-pointer-dereference in slgt_clean().(CVE-2022-49307)

    tipc: move bc link creation back to tipc_node_create(CVE-2022-49664)

    icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.(CVE-2022-49632)

    xprtrdma: treat all calls not a bcall when bc_serv is NULL(CVE-2022-49321)

    net: phy: micrel: Allow probing without .driver_data(CVE-2022-49472)

    tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept.(CVE-2022-49601)

    ip: Fix data-races around sysctl_ip_fwd_update_priority.(CVE-2022-49603)

    igb: fix a use-after-free issue in igb_clean_tx_ring(CVE-2022-49695)

    rxrpc: Fix listen() setting the bar too high for the prealloc rings(CVE-2022-49450)

    tty: fix deadlock caused by calling printk() under tty_port-lock(CVE-2022-49441)

    media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init(CVE-2022-49478)

    ima: Fix a potential integer overflow in ima_appraise_measurement(CVE-2022-49643)

    scsi: qla2xxx: Fix scheduling while atomic(CVE-2022-49156)

    mm/mempolicy: fix uninit-value in mpol_rebind_policy().(CVE-2022-49567)

    dm raid: fix KASAN warning in raid5_add_disks(CVE-2022-49673)

    padata: avoid UAF for reorder_work(CVE-2025-21726)

    ARM: hisi: Add missing of_node_put after of_find_compatible_node(CVE-2022-49447)

    ptp: Ensure info-enable callback is always set(CVE-2025-21814)

    bpf: Send signals asynchronously if !preemptible(CVE-2025-21728)

    ext4: don't BUG if someone dirty pages without asking ext4 first(CVE-2022-49171)

    ext4: fix ext4_mb_mark_bb() with flex_bg with fast_commit(CVE-2022-49174)

    dax: make sure inodes are flushed before destroy cache(CVE-2022-49220)

    ext4: avoid cycles in directory h-tree(CVE-2022-49343)

    ext4: fix bug_on in ext4_writepages(CVE-2022-49347)

    ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state(CVE-2022-49348)

    ext4: fix use-after-free in ext4_rename_dir_prepare(CVE-2022-49349)

    ext4: fix warning in ext4_handle_inode_extension(CVE-2022-49352)

    PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store().(CVE-2022-49434)

    x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails(CVE-2022-49549)

    scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI(CVE-2022-49535)

    crypto: qat - add param check for RSA(CVE-2022-49563)

    dmaengine: idxd: Fix the error handling path in idxd_cdev_register()(CVE-2022-49422)

    RDMA/mlx5: Fix memory leak in error flow for subscribe event routine(CVE-2022-49206)

    bpf, arm64: Clear prog-jited_len along prog-jited(CVE-2022-49341)

    bpf: Fix UAF due to race between btf_try_get_module and load_module(CVE-2022-49236)

    bpf: Fix potential array overflow in bpf_trampoline_get_progs().(CVE-2022-49548)

    bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals(CVE-2022-49658)

    zsmalloc: fix races between asynchronous zspage free and page migration(CVE-2022-49554)

    tpm: fix reference counting for struct tpm_chip(CVE-2022-49287)

    netfilter: nf_tables: initialize registers in nft_do_chain().(CVE-2022-49293)

    dm ioctl: prevent potential spectre v1 gadget(CVE-2022-49122)

    scsi: sd: Fix potential NULL pointer dereference(CVE-2022-49376)

    sysctl: Fix data races in proc_douintvec_minmax().(CVE-2022-49640)

    sysctl: Fix data races in proc_douintvec().(CVE-2022-49641)

    scsi: libfc: Fix use after free in fc_exch_abts_resp().(CVE-2022-49114)

    nbd: don't allow reconnect after disconnect(CVE-2025-21731)

    tpm: use try_get_ops() in tpm-space.c(CVE-2022-49286)

    cifs: potential buffer overflow in handling symlinks(CVE-2022-49058)

    extcon: Modify extcon device to be created after driver data is set(CVE-2022-49308)

    bfq: Update cgroup information before merging bio(CVE-2022-49413)

    cifs: prevent bad output lengths in smb2_ioctl_query_info().(CVE-2022-49271)

    media: cx24116: prevent overflows on SNR calculus(CVE-2024-50290)

    thermal/core: Fix memory leak in __thermal_cooling_device_register().(CVE-2022-49468)

    nbd: call genl_unregister_family() first in nbd_cleanup().(CVE-2022-49295)

    blk-mq: don't touch -tagset in blk_mq_get_sq_hctx(CVE-2022-49377)

    bfq: Make sure bfqg for which we are queueing requests is online(CVE-2022-49411)

    nvdimm: Fix firmware activation deadlock scenarios(CVE-2022-49446)

    nbd: fix io hung while disconnecting device(CVE-2022-49297)

    crypto: qat - add param check for DH(CVE-2022-49564)

    nbd: fix race between nbd_alloc_config() and module removal(CVE-2022-49300)

    net: usb: rtl8150: enable basic endpoint checking(CVE-2025-21708)

    scsi: target: tcmu: Fix possible page UAF(CVE-2022-49053)

    block: don't delete queue kobject before its children(CVE-2022-49259)

    md/bitmap: don't set sb values if can't pass sanity check(CVE-2022-49526)

    mm/slub: add missing TID updates on slab deactivation(CVE-2022-49700)

    block: Fix handling of offline queues in blk_mq_alloc_request_hctx().(CVE-2022-49720)

    ext4: fix race condition between ext4_write and ext4_convert_inline_data(CVE-2022-49414)

    ext4: fix bug_on in __es_tree_search(CVE-2022-49409)

    net: hns3: fix oops when unload drivers paralleling(CVE-2025-21802)

    irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions(CVE-2022-49715)

    mm/mempolicy: fix mpol_new leak in shared_policy_replace(CVE-2022-49080)

    ext4: fix bug_on ext4_mb_use_inode_pa(CVE-2022-49708)

    ext4: add reserved GDT blocks check(CVE-2022-49707)

    irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions(CVE-2022-49716)

    mm: fix unexpected zeroed page mapping with zram swap(CVE-2022-49052)

    scsi: qla2xxx: Fix crash during module load unload test(CVE-2022-49160)

    sctp: sysctl: rto_min/max: avoid using current-nsproxy(CVE-2025-21639)

    crypto: qat - fix memory leak in RSA(CVE-2022-49566)

    net/mlx5: Fix variable not being completed when function returns(CVE-2025-21662)

    scsi: storvsc: Ratelimit warning logs to prevent VM denial of service(CVE-2025-21690)

    vfio/platform: check the bounds of read/write syscalls(CVE-2025-21687)

    USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb().(CVE-2025-21689)

    ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init().(CVE-2024-53680)

    bpf: fix recursive lock when verdict program return SK_PASS(CVE-2024-56694)

    mm: zswap: properly synchronize freeing resources during CPU hotunplug(CVE-2025-21693)

    filemap: avoid truncating 64-bit offset to 32 bits(CVE-2025-21665)

    iomap: avoid avoid truncating 64-bit offset to 32 bits(CVE-2025-21667)

    fs/proc: fix softlockup in __read_vmcore (part 2).(CVE-2025-21694)

    net: hns3: don't auto enable misc vector(CVE-2025-21651)

    netfilter: conntrack: clamp maximum hashtable size to INT_MAX(CVE-2025-21648)

    net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute(CVE-2025-21653)

    netfilter: ipset: Hold module reference while requesting a module(CVE-2024-56637)

    sctp: sysctl: auth_enable: avoid using current-nsproxy(CVE-2025-21638)

    sctp: sysctl: cookie_hmac_alg: avoid using current-nsproxy(CVE-2025-21640)

    af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK(CVE-2024-57901)

    net: sched: fix ordering of qlen adjustment(CVE-2024-53164)

    af_packet: fix vlan_get_tci() vs MSG_PEEK(CVE-2024-57902)

    geneve: do not assume mac header is set in geneve_xmit_skb().(CVE-2024-56636)

    RDMA/rxe: Remove the direct link to net_device(CVE-2024-57795)

    net/ipv6: release expired exception dst cached in socket(CVE-2024-56644)

    NFSD: Prevent NULL dereference in nfsd4_process_cb_update()(CVE-2024-53217)

    iommu/arm-smmu: Defer probe of clients after smmu device bound(CVE-2024-56568)

    net/sctp: Prevent autoclose integer overflow in sctp_association_init().(CVE-2024-57938)

    dlm: fix possible lkb_resource null dereference(CVE-2024-47809)

    vsock/virtio: discard packets if the transport changes(CVE-2025-21669)

    vsock: prevent null-ptr-deref in vsock_*[has_data|has_space](CVE-2025-21666)

    netfilter: nf_tables: adapt set backend to use GC transaction API(CVE-2023-52923)

    RDMA/uverbs: Prevent integer overflow issue(CVE-2024-57890)

    pinmux: Use sequential access to access desc-pinmux data(CVE-2024-47141)

    drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req().(CVE-2024-57798)

    selinux: ignore unknown extended permissions(CVE-2024-57931)

    eth: bnxt: always recalculate features after XDP clearing, fix null-deref(CVE-2025-21682)

    net: restrict SO_REUSEPORT to inet sockets(CVE-2024-57903)

    bpf: Fix bpf_sk_select_reuseport() memory leak(CVE-2025-21683)

    sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket(CVE-2024-53168)

    net: macsec: Fix offload support for NETDEV_UNREGISTER event(CVE-2022-48720)

    netfilter: nf_set_pipapo: fix initial map fill(CVE-2024-57947)

    RDMA/hfi1: Fix use-after-free bug for mm struct(CVE-2022-49076)

    tipc: fix use-after-free Read in tipc_named_reinit(CVE-2022-49696)

    net: bonding: fix use-after-free after 802.3ad slave unbind(CVE-2022-49667)

    usbnet: fix memory leak in error case(CVE-2022-49589)

    sfc: fix use after free when disabling sriov(CVE-2022-49626)

Tenable has extracted the preceding description block directly from the EulerOS kernel security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

リモートの SUSE Linux SLES15 / SLES_SAP15 ホストには、SUSE-SU-2025:1241-1 のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。

    SUSE Linux Enterprise 15 SP5 カーネルが更新され、さまざまなセキュリティバグ修正が行われています。

    次のセキュリティバグを修正しました。

    - CVE-2022-49053：scsi：target：tcmu：潜在的なページ UAF を修正します（bsc#1237918）。
    - CVE-2022-49465：blk-throttle：bio が調整されているときに BIO_THROTTLED を設定します（bsc#1238919）。
    - CVE-2022-49739：gfs2：インライン inode の inode サイズを常にチェックします（bsc#1240207）。
    - CVE-2023-52935：mm/khugepaged：->anon_vma の競合を修正します（bsc#1240276）。
    - CVE-2024-53124：net：sk->sk_forward_alloc 周辺のデータ競合を修正します（bsc#1234074）。
    - CVE-2024-53176: smb: アンマウント中に、キャッシュされたすべての dir インスタンスが dentry を確実にドロップするようにします (bsc#1234894)。
    - CVE-2024-53178: smb: 再接続が open_cached_dir と競合する際に cfid を漏洩しません (bsc#1234895)。
    - CVE-2024-56651：can: hi311x：hi3110_can_ist()：潜在的な use-after-free を修正します（bsc#1235528）。
    - CVE-2024-57996: net_sched: sch_sfq: 1 パケット制限を許可しません (bsc#1239076)。
    - CVE-2024-58013：Bluetooth： MGMT：mgmt_remove_adv_monitor_sync の slab-use-after-free 読み取りを修正（bsc#1239095）。
    - CVE-2024-58014: wifi: brcmsmac: wlc_phy_iqcal_gainparams_nphy() にゲイン範囲チェックを追加しました (bsc#1239109)。
    - CVE-2025-21693：mm：zswap：CPU ホットアンプラグ中に適切に同期してリソースを解放します（bsc#1237029）。
    - CVE-2025-21718: net: rose: ユーザースレッドに対するタイマーの競合状態を修正しました (bsc#1239073)。
    - CVE-2025-21772：パーティション：mac：偽造パーティションテーブルの処理を修正します（bsc#1238911）。
    - CVE-2025-21780: drm/amdgpu: smu_sys_set_pp_table() のバッファオーバーフローのアタッチを回避します (bsc#1239115)。


Tenable は、前述の記述ブロックを SUSE セキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

遠端 Redhat Enterprise Linux 9 主機上安裝的多個套件受到 RHSA-2023:2458 公告中提及的多個弱點影響。

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    安全性修正：

    * net/bluetooth/l2cap_core.c 中 l2cap_connect 和 l2cap_le_connect_req 中的釋放後使用問題 (CVE-2022-42896)

    * net/ulp接聽 ULP 通訊端時發生釋放後使用 (CVE-2023-0461)

    * cpuAMD CPU 可能會暫時執行超出無條件直接分支的範圍 (CVE-2021-26341)

    * FBIOPUT_VSCREENINFO ioctl 的惡意資料可能造成 OOB 寫入記憶體 (CVE-2021-33655)

    * drivers/tty/tty_buffers.c 中可能存在爭用情形 (CVE-2022-1462)

    * KVMkvm_mmu_invpcid_gva 中的 NULL 指標解除參照 (CVE-2022-1789)

    * free_pipe_info() 中的釋放後使用可導致權限提升 (CVE-2022-1882)

    * KVMnVMX結束巢狀來賓時遺漏 IBPB可導致 Spectre v2 攻擊 (CVE-2022-2196)

    * netfilternf_conntrack_irc 訊息處理問題 (CVE-2022-2663)

    * xfrm_probe_algs 中的爭用情形可導致 OOB 讀取/寫入 (CVE-2022-3028)

    * 檔案 net/ipv4/fib_semantics.c 的 fib_nh_match 發生超出邊界讀取 (CVE-2022-3435)

    * mm/hugetlb.c 中 hugetlb_no_page() 的爭用情形 (CVE-2022-3522)

    * ipv6_renew_options() 中發生記憶體洩漏 (CVE-2022-3524)

    * do_ipv6_setsockopt 中有關 icsk->icsk_af_ops 的資料爭用 (CVE-2022-3566)

    * sk->sk_prot 發生資料爭用 (CVE-2022-3567)

    * net/bluetooth/l2cap_core.c 檔案的 l2cap_recv_acldata 中發生記憶體洩漏 (CVE-2022-3619)

    * 在 mm/gup.c 中follow_page_pte 中的拒絕服務這是因為 pte 項目毒害所導致 (CVE-2022-3623)

    * 在 devlink_param_get 中的 devlink 重新載入失敗後發生釋放後使用 (CVE-2022-3625)

    * brcmfmac 中發生 USB 可存取緩衝區溢位 (CVE-2022-3628)

    * net/bluetooth/l2cap_core.c 中 l2cap_conn_del 中的釋放後使用瑕疵 (CVE-2022-3640)

    * 當 intel_gvt_dma_map_guest_page 函式失敗時在 split_2MB_gtt_entry 中發生雙重釋放 (CVE-2022-3707)

    * mptcp中斷連線時子流程遊走中的 NULL 指標解除參照 (CVE-2022-4128)

    * l2tp清除 sk_user_data 時遺漏鎖定可導致 NULL 指標解除參照 (CVE-2022-4129)

    * igmp當開啟和關閉 inet 通訊端時ip_check_mc_rcu 中發生釋放後使用 (CVE-2022-20141)

    * 使用 IMA 的鎖定繞過 (CVE-2022-21505)

    * drivers/net/can/usb/usb_8dev.c 中的 usb_8dev_start_xmit 發生雙重釋放 (CVE-2022-28388)

    * 網路後端可能造成 Linux netfront 使用已釋放的 SKB (XSA-405) (CVE-2022-33743)

    * unmap_mapping_range() 與 VM_PFNMAP 對應上的 munmap() 爭用導致過時 TLB 項目 (CVE-2022-39188)

    * TLB 排清作業在某些 KVM_VCPU_PREEMPTED 中遭到錯誤處理進而導致來賓運作失常 (CVE-2022-39189)

    * cfg80211_update_notlisted_nontrans() 中的 u8 溢位問題 (CVE-2022-41674)

    * 與分葉 anon_vma 重複使用相關的釋放後使用 (CVE-2022-42703)

    * 在 net/wireless/scan.c 中bss_ref_get 中的 bss_ref_get 存在釋放後使用 (CVE-2022-42720)

    * net/wireless/scan.c 的 cfg80211_add_nontrans_list 中存在 BSS 清單損毀 (CVE-2022-42721)

    * P2P 裝置信標保護中的拒絕服務 (CVE-2022-42722)

    * usbmon 驅動程式中的記憶體損毀 (CVE-2022-43750)

    * 流量控制子系統中的 NULL 指標解除參照 (CVE-2022-47929)

    * rawv6_push_pending_frames 中發生 NULL 指標解除參照 (CVE-2023-0394)

    * qdisc_graft() 中的爭用情形導致釋放後使用 (CVE-2023-0590)

    * fs/cifs/connect.c 中的無效指標主機名稱造成的釋放後使用 (CVE-2023-1195)

    * tipc_conn_close 中的拒絕服務 (CVE-2023-1382)

    如需安全性問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

    其他變更：

    如需有關此發行版本的詳細變更資訊，請參閱可從「參考資料」一節連結的 Red Hat Enterprise Linux 9.2 版本資訊。

Tenable 已直接從 Red Hat Enterprise Linux 安全公告擷取前置描述區塊。

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix UAF due to race between     btf_try_get_module and load_module While working on code to populate kfunc BTF ID sets for module BTF from     its initcall, I noticed that by the time the initcall is invoked, the module BTF can already be seen by     userspace (and the BPF verifier). The existing btf_try_get_module calls try_module_get which only fails if     mod->state == MODULE_STATE_GOING, i.e. it can increment module reference when module initcall is happening     in parallel. Currently, BTF parsing happens from MODULE_STATE_COMING notifier callback. At this point, the     module initcalls have not been invoked. The notifier callback parses and prepares the module BTF,     allocates an ID, which publishes it to userspace, and then adds it to the btf_modules list allowing the     kernel to invoke btf_try_get_module for the BTF. However, at this point, the module has not been fully     initialized (i.e. its initcalls have not finished). The code in module.c can still fail and free the     module, without caring for other users. However, nothing stops btf_try_get_module from succeeding between     the state transition from MODULE_STATE_COMING to MODULE_STATE_LIVE. This leads to a use-after-free issue     when BPF program loads successfully in the state transition, load_module's do_init_module call fails and     frees the module, and BPF program fd on close calls module_put for the freed module. Future patch has test     case to verify we don't regress in this area in future. There are multiple points after     prepare_coming_module (in load_module) where failure can occur and module loading can return error. We     illustrate and test for the race using the last point where it can practically occur (in module __init     function). An illustration of the race: CPU 0 CPU 1 load_module notifier_call(MODULE_STATE_COMING)     btf_parse_module btf_alloc_id // Published to userspace list_add(&btf_mod->list, btf_modules)     mod->init(...) ... ^ bpf_check | check_pseudo_btf_id | btf_try_get_module | returns true | ... ... |     module __init in progress return prog_fd | ... ... V if (ret < 0) free_module(mod) ... close(prog_fd) ...
    bpf_prog_free_deferred module_put(used_btf.mod) // use-after-free We fix this issue by setting a flag     BTF_MODULE_F_LIVE, from the notifier callback when MODULE_STATE_LIVE state is reached for the module, so     that we return NULL from btf_try_get_module for modules that are not fully formed. Since try_module_get     already checks that module is not in MODULE_STATE_GOING state, and that is the only transition a live     module can make before being removed from btf_modules list, this is enough to close the race and prevent     the bug. A later selftest patch crafts the race condition artifically to verify that it has been fixed,     and that verifier fails to load program (with ENXIO). Lastly, a couple of comments: 1. Even if this race     didn't exist, it seems more appropriate to only access resources (ksyms and kfuncs) of a fully formed     module which has been initialized completely. 2. This patch was born out of need for synchronization     against module initcall for the next patch, so it is needed for correctness even without the     aforementioned race condition. The BTF resources initialized by module initcall are set up once and then     only looked up, so just waiting until the initcall has finished ensures correct behavior. (CVE-2022-49236)

Note that Nessus relies on the presence of the package as reported by the vendor.

远程 Redhat Enterprise Linux 9 主机上安装的程序包受到 RHSA-2023:2458 公告中提及的多个漏洞影响。

    内核程序包中包含 Linux 内核，后者是任何 Linux 操作系统的核心。

    安全修复：

    * net/bluetooth/l2cap_core.c 内 l2cap_connect 和 l2cap_le_connect_req 中存在释放后使用CVE-2022-42896

    * net/ulp监听 ULP 套接字中的释放后使用 (CVE-2023-0461)

    * cpuAMD CPU 可能会在无条件直接分支之外暂时执行 (CVE-2021-26341)

    * FBIOPUT_VSCREENINFO ioctl 的恶意数据可能导致 OOB 写入内存 (CVE-2021-33655)

    * drivers/tty/tty_buffers.c 中可能的争用条件 (CVE-2022-1462)

    * KVMkvm_mmu_invpcid_gva 中的空指针取消引用 (CVE-2022-1789)

    * free_pipe_info() 中的释放后使用可导致权限升级 (CVE-2022-1882)

    * KVMnVMX从嵌套客户机退出时缺少 IBPB 可导致 Spectre v2 攻击CVE-2022-2196

    * netfilternf_conntrack_irc 消息处理问题 (CVE-2022-2663)

    * xfrm_probe_algs 中的争用条件可导致 OOB 读取/写入 (CVE-2022-3028)

    * net/ipv4/fib_semantics.c 文件的 fib_nh_match 中存在越界读取 (CVE-2022-3435)

    * mm/hugetlb.c 中 hugetlb_no_page() 中的争用条件 (CVE-2022-3522)

    * ipv6_renew_options() 中的内存泄漏 (CVE-2022-3524)

    * do_ipv6_setsockopt 中围绕 icsk->icsk_af_ops 的数据争用 (CVE-2022-3566)

    * 围绕 sk->sk_prot 的数据争用 (CVE-2022-3567)

    * 文件 net/bluetooth/l2cap_core.c 的 l2cap_recv_acldata 中存在内存泄漏 (CVE-2022-3619)

    * 由于 pte 条目中毒mm/gup.c 中的 follow_page_pte 中存在拒绝服务CVE-2022-3623

    * devlink_param_get 中 devlink 重新加载失败后的释放后使用 (CVE-2022-3625)

    * brcmfmac 中存在可通过 USB 访问的缓冲区溢出CVE-2022-3628

    * net/bluetooth/l2cap_core.c 中 l2cap_conn_del 中的释放后使用缺陷 (CVE-2022-3640)

    * 当函数 intel_gvt_dma_map_guest_page 失败时split_2MB_gtt_entry 中发生双重释放 (CVE-2022-3707)

    * mptcp断开连接时子流遍历中的空指针取消引用 (CVE-2022-4128)

    * l2tp清除 sk_user_data 时缺少锁定可导致空指针取消引用CVE-2022-4129

    * igmp打开和关闭 inet 套接字时 ip_check_mc_rcu 中的释放后使用 (CVE-2022-20141)

    * 使用 IMA 的锁定绕过 (CVE-2022-21505)

    * drivers/net/can/usb/usb_8dev.c 中 usb_8dev_start_xmit 中存在的双重释放 (CVE-2022-28388)

    * 网络后端可能导致 Linux netfront 使用释放的 SKB (XSA-405) (CVE-2022-33743)

    * VM_PFNMAP 映射中的 unmap_mapping_range() 与 munmap() 争用导致过时 TLB 条目 (CVE-2022-39188)

    * 某些 KVM_VCPU_PREEMPTED 中未正确处理 TLB 刷新操作导致客户机故障 (CVE-2022-39189)

    * cfg80211_update_notlisted_nontrans() 中的 u8 溢出问题 (CVE-2022-41674)

    * 与叶 anon_vma 双重重用有关的释放后使用 (CVE-2022-42703)

    * net/wireless/scan.c 中 bss_ref_get 中的释放后使用 (CVE-2022-42720)

    * net/wireless/scan.c 内 cfg80211_add_nontrans_list 中的 BSS 列表损坏 (CVE-2022-42721)

    * P2P 设备的信标保护中的拒绝服务 (CVE-2022-42722)

    * usbmon 驱动程序中的内存损坏 (CVE-2022-43750)

    * 流量控制子系统中的空指针取消引用 (CVE-2022-47929)

    * rawv6_push_pending_frames 中的空指针取消引用 (CVE-2023-0394)

    * 由于 qdisc_graft() 中的争用条件导致的释放后使用 (CVE-2023-0590)

    * fs/cifs/connect.c 中无效的指针主机名导致释放后使用 (CVE-2023-1195)

    * tipc_conn_close 中的拒绝服务 (CVE-2023-1382)

    有关上述安全问题的更多详细信息，包括其影响、CVSS 得分、致谢，以及其他相关信息，请参阅列于“参考”部分的 CVE 页面。

    其他变更：

    如需有关此发行版本的详细变更信息，请参阅可从“参考”部分链接的 Red Hat Enterprise Linux 9.2 版本说明。

Tenable 已直接从 Red Hat Enterprise Linux 安全公告中提取上述描述块。

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    xsk: Fix race at socket teardown(CVE-2022-49215)

    acct: perform last write from workqueue(CVE-2025-21846)

    nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags(CVE-2022-49492)

    drop_monitor: fix incorrect initialization order(CVE-2025-21862)

    iommu/arm-smmu-v3: check return value after calling platform_get_resource().(CVE-2022-49319)

    ipv4: Fix a data-race around sysctl_fib_sync_mem.(CVE-2022-49637)

    memcg: fix soft lockup in the OOM process(CVE-2024-57977)

    ima: Fix potential memory leak in ima_init_crypto().(CVE-2022-49627)

    rdma/cxgb4: Prevent potential integer overflow on 32bit(CVE-2024-57973)

    tracing: Make sure trace_printk() can output as soon as it can be used(CVE-2023-53007)

    trace_events_hist: add check for return value of 'create_hist_field'(CVE-2023-53005)

    Squashfs: fix handling and sanity checking of xattr_ids count(CVE-2023-52933)

    tcp: Fix a data-race around sysctl_tcp_probe_threshold.(CVE-2022-49595)

    tcp: Fix data-races around sysctl_tcp_min_snd_mss.(CVE-2022-49596)

    tcp: Fix data-races around sysctl_tcp_base_mss.(CVE-2022-49597)

    tcp: Fix data-races around sysctl_tcp_l3mdev_accept.(CVE-2022-49599)

    hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING(CVE-2025-21816)

    RDMA/hfi1: Prevent use of lock before it is initialized(CVE-2022-49433)

    openvswitch: fix lockup on tx to unregistering netdev with carrier(CVE-2025-21681)

    net: hns3: add vlan list lock to protect vlan list(CVE-2022-49182)

    driver: base: fix UAF when driver_attach failed(CVE-2022-49385)

    ubi: ubi_create_volume: Fix use-after-free when volume creation failed(CVE-2022-49388)

    rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read(CVE-2024-58069)

    lz4: fix LZ4_decompress_safe_partial read out of bound(CVE-2022-49078)

    um: Fix out-of-bounds read in LDT setup(CVE-2022-49395)

    KVM: Explicitly verify target vCPU is online in kvm_get_vcpu().(CVE-2024-58083)

    ipv6: mcast: extend RCU protection in igmp6_send().(CVE-2025-21759)

    vsock: Keep the binding until socket destruction(CVE-2025-21756)

    pps: Fix a use-after-free(CVE-2024-57979)

    RDMA/hfi1: Fix use-after-free bug for mm struct(CVE-2022-49076)

    padata: fix UAF in padata_reorder(CVE-2025-21727)

    net: bonding: fix use-after-free after 802.3ad slave unbind(CVE-2022-49667)

    netfilter: nf_tables: avoid skb access on nf_stolen(CVE-2022-49622)

    srcu: Tighten cleanup_srcu_struct() GP checks(CVE-2022-49651)

    openvswitch: use RCU protection in ovs_vport_cmd_fill_info().(CVE-2025-21761)

    cgroup: Use separate src/dst nodes when preloading css_sets for migration(CVE-2022-49647)

    ice: arfs: fix use-after-free when freeing @rx_cpu_rmap(CVE-2022-49063)

    sfc: fix use after free when disabling sriov(CVE-2022-49626)

    macsec: fix UAF bug for real_dev(CVE-2022-49390)

    ndisc: extend RCU protection in ndisc_send_skb().(CVE-2025-21760)

    nfsd: release svc_expkey(CVE-2024-53216)

    nfsd: make sure exp active before svc_export_show(CVE-2024-56558)

    net: sched: Disallow replacing of child qdisc from one parent to another(CVE-2025-21700)

    tipc: fix use-after-free Read in tipc_named_reinit(CVE-2022-49696)

    arp: use RCU protection in arp_xmit().(CVE-2025-21762)

    nfsd: clear acl_access/acl_default after releasing them(CVE-2025-21796)

    ndisc: use RCU protection in ndisc_alloc_skb().(CVE-2025-21764)

    neighbour: use RCU protection in __neigh_notify().(CVE-2025-21763)

    scsi: hisi_sas: Free irq vectors in order for v3 HW(CVE-2022-49118)

    drm/plane: Move range check for format_count earlier(CVE-2021-47659)

    USB: hub: Ignore non-compliant devices with too many configs or interfaces(CVE-2025-21776)

    MIPS: pgalloc: fix memory leak caused by pgd_free().(CVE-2022-49210)

    bpf: avoid holding freeze_mutex during mmap operation(CVE-2025-21853)

    ip: Fix data-races around sysctl_ip_fwd_use_pmtu.(CVE-2022-49604)

    linux/dim: Fix divide by 0 in RDMA DIM(CVE-2022-49670)

    HID: multitouch: Add NULL check in mt_input_configured(CVE-2024-58020)

    nfp: bpf: Add check for nfp_app_ctrl_msg_alloc().(CVE-2025-21848)

    net: tipc: fix possible refcount leak in tipc_sk_create()(CVE-2022-49620)

    bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full(CVE-2022-49209)

    net: remove two BUG() from skb_checksum_help().(CVE-2022-49497)

    usbnet: fix memory leak in error case(CVE-2022-49657)

    usbnet: fix memory leak in error case(CVE-2022-49589)

    ip: Fix a data-race around sysctl_ip_autobind_reuse.(CVE-2022-49600)

    cipso: Fix data-races around sysctl.(CVE-2022-49639)

    KVM: x86: Reject Hyper-V's SEND_IPI hypercalls if local APIC isn't in-kernel(CVE-2025-21779)

    nexthop: Fix data-races around nexthop_compat_mode.(CVE-2022-49629)

    tracing/histograms: Fix memory leak problem(CVE-2022-49648)

    SUNRPC: Fix the svc_deferred_event trace class(CVE-2022-49065)

    af_unix: Fix a data-race in unix_dgram_peer_wake_me().(CVE-2022-49344)

    usb: xhci: Fix NULL pointer dereference on certain command aborts(CVE-2024-57981)

    ceph: fix memory leak in ceph_readdir when note_last_dentry returns error(CVE-2022-49107)

    NFSv4.2: fix reference count leaks in _nfs42_proc_copy_notify().(CVE-2022-49103)

    io_uring: fix memory leak of uid in files registration(CVE-2022-49144)

    RDMA/cm: Fix memory leak in ib_cm_insert_listen(CVE-2022-49671)

    ip: Fix a data-race around sysctl_fwmark_reflect.(CVE-2022-49602)

    hwrng: cavium - fix NULL but dereferenced coccicheck error(CVE-2022-49177)

    mlxsw: spectrum: Guard against invalid local ports(CVE-2022-49134)

    raw: Fix a data-race around sysctl_raw_l3mdev_accept.(CVE-2022-49631)

    icmp: Fix data-races around sysctl.(CVE-2022-49638)

    tty: synclink_gt: Fix null-pointer-dereference in slgt_clean().(CVE-2022-49307)

    iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe().(CVE-2022-49323)

    drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes(CVE-2022-49532)

    scsi: qla2xxx: Suppress a kernel complaint in qla_create_qpair().(CVE-2022-49155)

    tipc: move bc link creation back to tipc_node_create(CVE-2022-49664)

    NFSv4: Don't hold the layoutget locks across multiple RPC calls(CVE-2022-49316)

    icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.(CVE-2022-49632)

    xprtrdma: treat all calls not a bcall when bc_serv is NULL(CVE-2022-49321)

    net: phy: micrel: Allow probing without .driver_data(CVE-2022-49472)

    tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept.(CVE-2022-49601)

    kernel/resource: fix kfree() of bootmem memory again(CVE-2022-49190)

    vrf: use RCU protection in l3mdev_l3_out().(CVE-2025-21791)

    tcp: Fix a data-race around sysctl_tcp_ecn_fallback.(CVE-2022-49630)

    i2c: dev: check return value when calling dev_set_name().(CVE-2022-49046)

    list: fix a data-race around ep-rdllist(CVE-2022-49443)

    perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()(CVE-2022-49607)

    drm/amd/display: Fix memory leak(CVE-2022-49135)

    ip: Fix data-races around sysctl_ip_fwd_update_priority.(CVE-2022-49603)

    media: uvcvideo: Fix double free in error path(CVE-2024-57980)

    io_uring: prevent opcode speculation(CVE-2025-21863)

    geneve: Fix use-after-free in geneve_find_dev().(CVE-2025-21858)

    arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array(CVE-2025-21785)

    igb: fix a use-after-free issue in igb_clean_tx_ring(CVE-2022-49695)

    rxrpc: Fix listen() setting the bar too high for the prealloc rings(CVE-2022-49450)

    tty: fix deadlock caused by calling printk() under tty_port-lock(CVE-2022-49441)

    media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init(CVE-2022-49478)

    ima: Fix a potential integer overflow in ima_appraise_measurement(CVE-2022-49643)

    scsi: qla2xxx: Fix scheduling while atomic(CVE-2022-49156)

    scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock(CVE-2022-49536)

    mm/mempolicy: fix uninit-value in mpol_rebind_policy().(CVE-2022-49567)

    KVM: VMX: Prevent RSB underflow before vmenter(CVE-2022-49610)

    dm raid: fix KASAN warning in raid5_add_disks(CVE-2022-49673)

    tpm: Change to kvalloc() in eventlog/acpi.c(CVE-2024-58005)

    media: uvcvideo: Remove dangling pointers(CVE-2024-58002)

    padata: avoid UAF for reorder_work(CVE-2025-21726)

    ARM: hisi: Add missing of_node_put after of_find_compatible_node(CVE-2022-49447)

    ptp: Ensure info-enable callback is always set(CVE-2025-21814)

    bpf: Send signals asynchronously if !preemptible(CVE-2025-21728)

    ext4: don't BUG if someone dirty pages without asking ext4 first(CVE-2022-49171)

    ext4: fix ext4_mb_mark_bb() with flex_bg with fast_commit(CVE-2022-49174)

    dax: make sure inodes are flushed before destroy cache(CVE-2022-49220)

    ext4: avoid cycles in directory h-tree(CVE-2022-49343)

    ext4: fix bug_on in ext4_writepages(CVE-2022-49347)

    ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state(CVE-2022-49348)

    ext4: fix use-after-free in ext4_rename_dir_prepare(CVE-2022-49349)

    ext4: fix warning in ext4_handle_inode_extension(CVE-2022-49352)

    PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store().(CVE-2022-49434)

    x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails(CVE-2022-49549)

    scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI(CVE-2022-49535)

    crypto: qat - add param check for RSA(CVE-2022-49563)

    dmaengine: idxd: Fix the error handling path in idxd_cdev_register()(CVE-2022-49422)

    RDMA/mlx5: Fix memory leak in error flow for subscribe event routine(CVE-2022-49206)

    bpf, arm64: Clear prog-jited_len along prog-jited(CVE-2022-49341)

    bpf: Fix UAF due to race between btf_try_get_module and load_module(CVE-2022-49236)

    bpf: Fix potential array overflow in bpf_trampoline_get_progs().(CVE-2022-49548)

    bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals(CVE-2022-49658)

    zsmalloc: fix races between asynchronous zspage free and page migration(CVE-2022-49554)

    tpm: fix reference counting for struct tpm_chip(CVE-2022-49287)

    netfilter: nf_tables: initialize registers in nft_do_chain().(CVE-2022-49293)

    dm ioctl: prevent potential spectre v1 gadget(CVE-2022-49122)

    scsi: sd: Fix potential NULL pointer dereference(CVE-2022-49376)

    sysctl: Fix data races in proc_douintvec_minmax().(CVE-2022-49640)

    sysctl: Fix data races in proc_douintvec().(CVE-2022-49641)

    scsi: libfc: Fix use after free in fc_exch_abts_resp().(CVE-2022-49114)

    nbd: don't allow reconnect after disconnect(CVE-2025-21731)

    tpm: use try_get_ops() in tpm-space.c(CVE-2022-49286)

    cifs: potential buffer overflow in handling symlinks(CVE-2022-49058)

    extcon: Modify extcon device to be created after driver data is set(CVE-2022-49308)

    bfq: Update cgroup information before merging bio(CVE-2022-49413)

    cifs: prevent bad output lengths in smb2_ioctl_query_info().(CVE-2022-49271)

    media: cx24116: prevent overflows on SNR calculus(CVE-2024-50290)

    thermal/core: Fix memory leak in __thermal_cooling_device_register().(CVE-2022-49468)

    nbd: call genl_unregister_family() first in nbd_cleanup().(CVE-2022-49295)

    blk-mq: don't touch -tagset in blk_mq_get_sq_hctx(CVE-2022-49377)

    bfq: Make sure bfqg for which we are queueing requests is online(CVE-2022-49411)

    nvdimm: Fix firmware activation deadlock scenarios(CVE-2022-49446)

    crypto: qat - add param check for DH(CVE-2022-49564)

    nbd: fix race between nbd_alloc_config() and module removal(CVE-2022-49300)

    nbd: fix io hung while disconnecting device(CVE-2022-49297)

    net: usb: rtl8150: enable basic endpoint checking(CVE-2025-21708)

    scsi: target: tcmu: Fix possible page UAF(CVE-2022-49053)

    block: don't delete queue kobject before its children(CVE-2022-49259)

    md/bitmap: don't set sb values if can't pass sanity check(CVE-2022-49526)

    mm/slub: add missing TID updates on slab deactivation(CVE-2022-49700)

    block: Fix handling of offline queues in blk_mq_alloc_request_hctx().(CVE-2022-49720)

    ext4: fix race condition between ext4_write and ext4_convert_inline_data(CVE-2022-49414)

    ext4: fix bug_on in __es_tree_search(CVE-2022-49409)

    net: hns3: fix oops when unload drivers paralleling(CVE-2025-21802)

    irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions(CVE-2022-49715)

    mm/mempolicy: fix mpol_new leak in shared_policy_replace(CVE-2022-49080)

    ext4: fix bug_on ext4_mb_use_inode_pa(CVE-2022-49708)

    ext4: add reserved GDT blocks check(CVE-2022-49707)

    irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions(CVE-2022-49716)

    mm: fix unexpected zeroed page mapping with zram swap(CVE-2022-49052)

    scsi: qla2xxx: Fix crash during module load unload test(CVE-2022-49160)

    sctp: sysctl: rto_min/max: avoid using current-nsproxy(CVE-2025-21639)

    crypto: qat - fix memory leak in RSA(CVE-2022-49566)

    net/mlx5: Fix variable not being completed when function returns(CVE-2025-21662)

    scsi: storvsc: Ratelimit warning logs to prevent VM denial of service(CVE-2025-21690)

    vfio/platform: check the bounds of read/write syscalls(CVE-2025-21687)

    USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb().(CVE-2025-21689)

    ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init().(CVE-2024-53680)

    bpf: fix recursive lock when verdict program return SK_PASS(CVE-2024-56694)

    mm: zswap: properly synchronize freeing resources during CPU hotunplug(CVE-2025-21693)

    ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up(CVE-2025-21887)

    net: asix: add proper error handling of usb read errors(CVE-2022-49226)

    mm/khugepaged: fix -anon_vma race(CVE-2023-52935)

    HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections(CVE-2024-57986)

    proc: fix UAF in proc_get_inode().(CVE-2025-21999)

    smb: client: Add check for next_buffer in receive_encrypted_standard().(CVE-2025-21844)

    exec: don't WARN for racy path_noexec check(CVE-2024-50010)

    kthread: unpark only parked kthread(CVE-2024-50019)

Tenable has extracted the preceding description block directly from the EulerOS kernel security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:1241-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.

    The following security bugs were fixed:

    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
    - CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
    - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58013: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync     (bsc#1239095).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

リモートの SUSE Linux SLES15 / SLES_SAP15 ホストには、SUSE-SU-2025:1027-1 のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。

    SUSE Linux Enterprise 15 SP4 カーネルが更新され、さまざまなセキュリティバグ修正が行われています。


    次のセキュリティバグを修正しました。

    - CVE-2024-2201: x86/BHI での情報漏洩を修正しました (bsc#1217339)。
    - CVE-2024-41092: drm/i915/gt: フェンスレジスタの取り消しによる潜在的なメモリ解放後使用 (Use After Free) を修正しました (bsc#1228483)。
    - CVE-2024-42098: crypto: ecdh - private_key を明示的にゼロ化します (bsc#1228779)。
    - CVE-2024-42229: crypto: aead,cipher - 使用後にキーバッファをゼロ化します (bsc#1228708)。
    - CVE-2024-57996: net_sched: sch_sfq: 1 パケット制限を許可しません (bsc#1239076)。
    - CVE-2024-58014: wifi: brcmsmac: wlc_phy_iqcal_gainparams_nphy() にゲイン範囲チェックを追加しました (bsc#1239109)。
    - CVE-2025-21718: net: rose: ユーザースレッドに対するタイマーの競合状態を修正しました (bsc#1239073)。
    - CVE-2025-21780: drm/amdgpu: smu_sys_set_pp_table() のバッファオーバーフローのアタッチを回避します (bsc#1239115)。


Tenable は、前述の記述ブロックを SUSE セキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

リモート Redhat Enterprise Linux 9 ホストに、RHSA-2023:2458 アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

    カーネルパッケージには、Linux オペレーティングシステムのコアである Linux カーネルが含まれています。

    セキュリティ修正プログラム：

    * net/bluetooth/l2cap_core.c の l2cap_connect および l2cap_le_connect_req の use-after-freeCVE-2022-42896

    * net/ulplisting ULP ソケットでの use-after-freeCVE-2023-0461

    * cpuAMD CPU が無条件のダイレクトブランチを超えて一時的に実行する可能性がありますCVE-2021-26341

    * FBIOPUT_VSCREENINFO ioctl の悪意のあるデータにより、OOB 書き込みメモリが発生する可能性がありますCVE-2021-33655

    * drivers/tty/tty_buffers.c の潜在的な競合状態CVE-2022-1462

    * KVMkvm_mmu_invpcid_gva の NULL ポインターデリファレンスCVE-2022-1789

    * free_pipe_info() の use-after-free は権限昇格を引き起こす可能性がありますCVE-2022-1882

    * KVMnVMXネストされたゲストから終了する際に IBPB がないために、Spectre v2 攻撃が引き起こされる可能性がありますCVE-2022-2196

    * netfilternf_conntrack_irc メッセージ処理の問題CVE-2022-2663

    * xfrm_probe_algs の競合状態が、OOB 読み取り/書き込みを引き起こす可能性がありますCVE-2022-3028

    * net/ipv4/fib_semantics.c ファイルの fib_nh_match での領域外読み取りCVE-2022-3435

    * mm/hugetlb.c の hugetlb_no_page() における競合状態CVE-2022-3522

    * ipv6_renew_options() でのメモリリークCVE-2022-3524

    * do_ipv6_setsockopt の icsk->icsk_af_ops 周辺のデータ競合CVE-2022-3566

    * sk->sk_prot 周辺のデータ競合CVE-2022-3567

    * ファイル net/bluetooth/l2cap_core.c の l2cap_recv_acldata のメモリ漏洩CVE-2022-3619

    * ポイズニングされた pte エントリによる、mm/gup.c の follow_page_pte のサービス拒否CVE-2022-3623

    * devlink_param_get で devlink リロードに失敗した後の use-after-freeCVE-2022-3625

    * brcmfmac での USB アクセス可能なバッファオーバーフローCVE-2022-3628

    * net/bluetooth/l2cap_core.c の l2cap_conn_del における use-after-free 欠陥CVE-2022-3640

    * 関数 intel_gvt_dma_map_guest_page が失敗した際の split_2MB_gtt_entry の二重解放CVE-2022-3707

    * mptcp切断時のサブフロートラバーサルの NULL ポインターデリファレンスCVE-2022-4128

    * l2tpsk_user_data のクリア時にロックがないために、NULL ポインターデリファレンスが起こる可能性がありますCVE-2022-4129

    * igmpinet ソケットを開いて閉じる際の ip_check_mc_rcu における use-after-freeCVE-2022-20141

    * IMA を使用したロックダウンバイパスCVE-2022-21505

    * drivers/net/can/usb/usb_8dev.c の usb_8dev_start_xmit の二重解放CVE-2022-28388

    * ネットワークバックエンドにより、Linux netfront が解放された SKB を使用する可能性がありますXSA-405CVE-2022-33743

    * VM_PFNMAP マッピングでの munmap() との unmap_mapping_range() の競合により、古い TLB エントリが発生しますCVE-2022-39188]

    * TLB フラッシュ操作が特定の KVM_VCPU_PREEMPTED で誤って処理され、ゲストの誤動作を引き起こしますCVE-2022-39189

    * cfg80211_update_notlisted_nontrans() の u8 オーバーフロー問題CVE-2022-41674

    * リーフ anon_vma の二重再利用に関連する use-after-freeCVE-2022-42703

    * net/wireless/scan.c の bss_ref_get における use-after-freeCVE-2022-42720

    * net/wireless/scan.c の cfg80211_add_nontrans_list の BSS リスト破損CVE-2022-42721

    * P2P デバイス用のビーコン保護でのサービス拒否CVE-2022-42722

    * usbmon ドライバーでのメモリ破損CVE-2022-43750

    * トラフィックコントロールサブシステムの NULL ポインターデリファレンスCVE-2022-47929

    * rawv6_push_pending_frames の NULL ポインターデリファレンスCVE-2023-0394

    * qdisc_graft() の競合状態による use-after-freeCVE-2023-0590

    * fs/cifs/connect.c の無効なポインターホスト名によって引き起こされる use-after-freeCVE-2023-1195

    * tipc_conn_close のサービス拒否CVE-2023-1382

    影響、CVSS スコア、謝辞、その他の関連情報を含むセキュリティ問題の詳細については、「参照」セクションに記載されている CVE のページを参照してください。

    追加の変更:

    このリリースの変更に関する詳細については、「参照」セクションからリンクされている Red Hat Enterprise Linux 9.2 リリースノートを参照してください。

Tenable は、前述の記述ブロックを Red Hat Enterprise Linux セキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:2458 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * use-after-free in l2cap_connect and l2cap_le_connect_req in net/bluetooth/l2cap_core.c (CVE-2022-42896)

    * net/ulp: use-after-free in listening ULP sockets (CVE-2023-0461)

    * cpu: AMD CPUs may transiently execute beyond unconditional direct branch (CVE-2021-26341)

    * malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory (CVE-2021-33655)

    * possible race condition in drivers/tty/tty_buffers.c (CVE-2022-1462)

    * KVM: NULL pointer dereference in kvm_mmu_invpcid_gva (CVE-2022-1789)

    * use-after-free in free_pipe_info() could lead to privilege escalation (CVE-2022-1882)

    * KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks (CVE-2022-2196)

    * netfilter: nf_conntrack_irc message handling issue (CVE-2022-2663)

    * race condition in xfrm_probe_algs can lead to OOB read/write (CVE-2022-3028)

    * out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c (CVE-2022-3435)

    * race condition in hugetlb_no_page() in mm/hugetlb.c (CVE-2022-3522)

    * memory leak in ipv6_renew_options() (CVE-2022-3524)

    * data races around icsk->icsk_af_ops in do_ipv6_setsockopt (CVE-2022-3566)

    * data races around sk->sk_prot (CVE-2022-3567)

    * memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c (CVE-2022-3619)

    * denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry (CVE-2022-3623)

    * use-after-free after failed devlink reload in devlink_param_get (CVE-2022-3625)

    * USB-accessible buffer overflow in brcmfmac (CVE-2022-3628)

    * use after free flaw in l2cap_conn_del in net/bluetooth/l2cap_core.c (CVE-2022-3640)

    * Double-free in split_2MB_gtt_entry when function intel_gvt_dma_map_guest_page failed (CVE-2022-3707)

    * mptcp: NULL pointer dereference in subflow traversal at disconnect time (CVE-2022-4128)

    * l2tp: missing lock when clearing sk_user_data can lead to NULL pointer dereference (CVE-2022-4129)

    * igmp: use-after-free in ip_check_mc_rcu when opening and closing inet sockets (CVE-2022-20141)

    * lockdown bypass using IMA (CVE-2022-21505)

    * double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c (CVE-2022-28388)

    * network backend may cause Linux netfront to use freed SKBs (XSA-405) (CVE-2022-33743)

    * unmap_mapping_range() race with munmap() on VM_PFNMAP mappings leads to stale TLB entry (CVE-2022-39188)

    * TLB flush operations are mishandled in certain KVM_VCPU_PREEMPTED leading to guest malfunctioning     (CVE-2022-39189)

    * u8 overflow problem in cfg80211_update_notlisted_nontrans() (CVE-2022-41674)

    * use-after-free related to leaf anon_vma double reuse (CVE-2022-42703)

    * use-after-free in bss_ref_get in net/wireless/scan.c (CVE-2022-42720)

    * BSS list corruption in cfg80211_add_nontrans_list in net/wireless/scan.c (CVE-2022-42721)

    * Denial of service in beacon protection for P2P-device (CVE-2022-42722)

    * memory corruption in usbmon driver (CVE-2022-43750)

    * NULL pointer dereference in traffic control subsystem (CVE-2022-47929)

    * NULL pointer dereference in rawv6_push_pending_frames (CVE-2023-0394)

    * use-after-free due to race condition in qdisc_graft() (CVE-2023-0590)

    * use-after-free caused by invalid pointer hostname in fs/cifs/connect.c (CVE-2023-1195)

    * denial of service in tipc_conn_close (CVE-2023-1382)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.2 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:1027-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
    - CVE-2024-41092: drm/i915/gt: Fix potential UAF by revoke of fence registers (bsc#1228483).
    - CVE-2024-42098: crypto: ecdh - explicitly zeroize private_key (bsc#1228779).
    - CVE-2024-42229: crypto: aead,cipher - zeroize key buffer after use (bsc#1228708).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
225146	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49236	Nessus	Misc.	2025/3/5	2025/10/17	high
225146	Linux Distros 未修补的漏洞: CVE-2022-49236	Nessus	Misc.	2025/3/5	2025/10/17	high
225146	Linux Distros 未修補弱點：CVE-2022-49236	Nessus	Misc.	2025/3/5	2025/10/17	high
238210	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1618)	Nessus	Huawei Local Security Checks	2025/6/11	2025/6/11	high
234407	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	2025/4/15	2025/9/24	high
175477	RHEL 9：核心 (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	2023/5/13	2025/9/10	high
225146	Linux Distros Unpatched Vulnerability : CVE-2022-49236	Nessus	Misc.	2025/3/5	2025/10/17	high
238226	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1635)	Nessus	Huawei Local Security Checks	2025/6/11	2025/6/11	high
175477	RHEL 9：内核 (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	2023/5/13	2025/9/10	high
238182	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2025-1589)	Nessus	Huawei Local Security Checks	2025/6/11	2025/6/11	high
234407	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	2025/4/15	2025/9/24	high
233410	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	2025/3/27	2025/9/24	high
175477	RHEL 9 : kernel (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	2023/5/13	2025/9/10	high
175477	RHEL 9 : kernel (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	2023/5/13	2025/9/10	high
233410	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	2025/3/27	2025/9/24	high
238183	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2025-1590)	Nessus	Huawei Local Security Checks	2025/6/11	2025/6/11	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high