In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way.

The CentOS Linux 8.4 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.4:CLSA-2025:1763731262 advisory.

  - An issue was discovered on Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3     implementations accept plaintext A-MSDU frames as long as the first 8 bytes correspond to a valid RFC1042     (i.e., LLC/SNAP) header for EAPOL. An adversary can abuse this to inject arbitrary network packets     independent of the network configuration. (CVE-2020-26144)

  - An issue was discovered in the Linux kernel before 5.11.8. kernel/bpf/verifier.c performs undesirable out-     of-bounds speculation on pointer arithmetic, leading to side-channel attacks that defeat Spectre     mitigations and obtain sensitive information from kernel memory, aka CID-f232326f6966. This affects     pointer types that do not define a ptr_limit. (CVE-2020-27170)

  - An issue was discovered in the Linux kernel before 5.11.8. kernel/bpf/verifier.c has an off-by-one error     (with a resultant integer underflow) affecting out-of-bounds speculation on pointer arithmetic, leading to     side-channel attacks that defeat Spectre mitigations and obtain sensitive information from kernel memory,     aka CID-10d2bb2e6b1d. (CVE-2020-27171)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix use-after-free     warning Fix the following use-after-free warning which is observed during controller reset: refcount_t:
    underflow; use-after-free. WARNING: CPU: 23 PID: 5399 at lib/refcount.c:28     refcount_warn_saturate+0xa6/0xf0 (CVE-2022-48695)

  - In the Linux kernel, the following vulnerability has been resolved: ASoC: ops: Reject out of bounds values     in snd_soc_put_volsw() We don't currently validate that the values being set are within the range we     advertised to userspace as being valid, do so and reject any values that are out of range.
    (CVE-2022-48738)

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

The CentOS Linux 8.5 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.5:CLSA-2025:1763734783 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix use-after-free     warning Fix the following use-after-free warning which is observed during controller reset: refcount_t:
    underflow; use-after-free. WARNING: CPU: 23 PID: 5399 at lib/refcount.c:28     refcount_warn_saturate+0xa6/0xf0 (CVE-2022-48695)

  - In the Linux kernel, the following vulnerability has been resolved: ASoC: ops: Reject out of bounds values     in snd_soc_put_volsw() We don't currently validate that the values being set are within the range we     advertised to userspace as being valid, do so and reject any values that are out of range.
    (CVE-2022-48738)

  - In the Linux kernel, the following vulnerability has been resolved: rpmsg: char: Fix race between the     release of rpmsg_ctrldev and cdev struct rpmsg_ctrldev contains a struct cdev. The current code frees the     rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the cdev is a managed object, therefore its     release is not predictable and the rpmsg_ctrldev could be freed before the cdev is entirely released, as     in the backtrace below. [ 93.625603] ODEBUG: free active (active state 0) object type: timer_list hint:
    delayed_work_timer_fn+0x0/0x7c [ 93.636115] WARNING: CPU: 0 PID: 12 at lib/debugobjects.c:488     debug_print_object+0x13c/0x1b0 [ 93.644799] Modules linked in: veth xt_cgroup xt_MASQUERADE rfcomm     algif_hash algif_skcipher af_alg uinput ip6table_nat fuse uvcvideo videobuf2_vmalloc venus_enc venus_dec     videobuf2_dma_contig hci_uart btandroid btqca snd_soc_rt5682_i2c bluetooth qcom_spmi_temp_alarm     snd_soc_rt5682v [ 93.715175] CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: G B 5.4.163-lockdep #26 [     93.723855] Hardware name: Google Lazor (rev3 - 8) with LTE (DT) [ 93.730055] Workqueue: events     kobject_delayed_cleanup [ 93.735271] pstate: 60c00009 (nZCv daif +PAN +UAO) [ 93.740216] pc :
    debug_print_object+0x13c/0x1b0 [ 93.744890] lr : debug_print_object+0x13c/0x1b0 [ 93.749555] sp :
    ffffffacf5bc7940 [ 93.752978] x29: ffffffacf5bc7940 x28: dfffffd000000000 [ 93.758448] x27:
    ffffffacdb11a800 x26: dfffffd000000000 [ 93.763916] x25: ffffffd0734f856c x24: dfffffd000000000 [     93.769389] x23: 0000000000000000 x22: ffffffd0733c35b0 [ 93.774860] x21: ffffffd0751994a0 x20:
    ffffffd075ec27c0 [ 93.780338] x19: ffffffd075199100 x18: 00000000000276e0 [ 93.785814] x17:
    0000000000000000 x16: dfffffd000000000 [ 93.791291] x15: ffffffffffffffff x14: 6e6968207473696c [     93.796768] x13: 0000000000000000 x12: ffffffd075e2b000 [ 93.802244] x11: 0000000000000001 x10:
    0000000000000000 [ 93.807723] x9 : d13400dff1921900 x8 : d13400dff1921900 [ 93.813200] x7 :
    0000000000000000 x6 : 0000000000000000 [ 93.818676] x5 : 0000000000000080 x4 : 0000000000000000 [     93.824152] x3 : ffffffd0732a0fa4 x2 : 0000000000000001 [ 93.829628] x1 : ffffffacf5bc7580 x0 :
    0000000000000061 [ 93.835104] Call trace: [ 93.837644] debug_print_object+0x13c/0x1b0 [ 93.841963]
    __debug_check_no_obj_freed+0x25c/0x3c0 [ 93.846987] debug_check_no_obj_freed+0x18/0x20 [ 93.851669]     slab_free_freelist_hook+0xbc/0x1e4 [ 93.856346] kfree+0xfc/0x2f4 [ 93.859416]     rpmsg_ctrldev_release_device+0x78/0xb8 [ 93.864445] device_release+0x84/0x168 [ 93.868310]     kobject_cleanup+0x12c/0x298 [ 93.872356] kobject_delayed_cleanup+0x10/0x18 [ 93.876948]     process_one_work+0x578/0x92c [ 93.881086] worker_thread+0x804/0xcf8 [ 93.884963] kthread+0x2a8/0x314 [     93.888303] ret_from_fork+0x10/0x18 The cdev_device_add/del() API was created to address this issue (see     commit '233ed09d7fda (chardev: add helper function to register char devs with a struct device)'), use it     instead of cdev add/del(). (CVE-2022-48759)

  - In the Linux kernel, the following vulnerability has been resolved: dm integrity: fix memory corruption     when tag_size is less than digest size It is possible to set up dm-integrity in such a way that the     tag_size parameter is less than the actual digest size. In this situation, a part of the digest beyond     tag_size is ignored. In this case, dm-integrity would write beyond the end of the ic->recalc_tags array     and corrupt memory. The corruption happened in     integrity_recalc->integrity_sector_checksum->crypto_shash_final. Fix this corruption by increasing the     tags array so that it has enough padding at the end to accomodate the loop in integrity_recalc() being     able to write a full digest size for the last member of the tags array. (CVE-2022-49044)

  - In the Linux kernel, the following vulnerability has been resolved: ata: sata_dwc_460ex: Fix crash due to     OOB write the driver uses libata's tag values from in various arrays. Since the mentioned patch bumped     the ATA_TAG_INTERNAL to 32, the value of the SATA_DWC_QCMD_MAX needs to account for that. Otherwise     ATA_TAG_INTERNAL usage cause similar crashes like this as reported by Tice Rex on the OpenWrt Forum and     reproduced (with symbols) here: | BUG: Kernel NULL pointer dereference at 0x00000000 | Faulting     instruction address: 0xc03ed4b8 | Oops: Kernel access of bad area, sig: 11 [#1] | BE PAGE_SIZE=4K PowerPC     44x Platform | CPU: 0 PID: 362 Comm: scsi_eh_1 Not tainted 5.4.163 #0 | NIP: c03ed4b8 LR: c03d27e8 CTR:
    c03ed36c | REGS: cfa59950 TRAP: 0300 Not tainted (5.4.163) | MSR: 00021000 <CE,ME> CR: 42000222 XER:
    00000000 | DEAR: 00000000 ESR: 00000000 | GPR00: c03d27e8 cfa59a08 cfa55fe0 00000000 0fa46bc0 [...] | [..]     | NIP [c03ed4b8] sata_dwc_qc_issue+0x14c/0x254 | LR [c03d27e8] ata_qc_issue+0x1c8/0x2dc | Call Trace: |     [cfa59a08] [c003f4e0] __cancel_work_timer+0x124/0x194 (unreliable) | [cfa59a78] [c03d27e8]     ata_qc_issue+0x1c8/0x2dc | [cfa59a98] [c03d2b3c] ata_exec_internal_sg+0x240/0x524 | [cfa59b08] [c03d2e98]     ata_exec_internal+0x78/0xe0 | [cfa59b58] [c03d30fc] ata_read_log_page.part.38+0x1dc/0x204 | [cfa59bc8]     [c03d324c] ata_identify_page_supported+0x68/0x130 | [...] This is because sata_dwc_dma_xfer_complete()     NULLs the dma_pending's next neighbour chan (a *dma_chan struct) in this '32' case right here (line     ~735): > hsdevp->dma_pending[tag] = SATA_DWC_DMA_PENDING_NONE; Then the next time, a dma gets issued;
    dma_dwc_xfer_setup() passes the NULL'd hsdevp->chan to the dmaengine_slave_config() which then causes the     crash. With this patch, SATA_DWC_QCMD_MAX is now set to ATA_MAX_QUEUE + 1. This avoids the OOB. But please     note, there was a worthwhile discussion on what ATA_TAG_INTERNAL and ATA_MAX_QUEUE is. And why there     should not be a fake 33 command-long queue size. Ideally, the dw driver should account for the     ATA_TAG_INTERNAL. In Damien Le Moal's words: ... having looked at the driver, it is a bigger change than     just faking a 33rd tag that is in fact not a command tag at all. BugLink:
    https://github.com/openwrt/openwrt/issues/9505 (CVE-2022-49073)

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

An update of the linux package has been released.

The version of kernel installed on the remote host is prior to 5.15.189-131.211. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2025-088 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    dma-buf/dma-resv: check if the new fence is really later (CVE-2022-49935)

    In the Linux kernel, the following vulnerability has been resolved:

    mptcp: do not queue data on closed subflows (CVE-2022-50070)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (CVE-2025-38162)

    In the Linux kernel, the following vulnerability has been resolved:

    fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var (CVE-2025-38215)

    In the Linux kernel, the following vulnerability has been resolved:

    af_unix: Don't leave consecutive consumed OOB skbs. (CVE-2025-38236)

    In the Linux kernel, the following vulnerability has been resolved:

    bridge: mcast: Fix use-after-free during router port configuration (CVE-2025-38248)

    In the Linux kernel, the following vulnerability has been resolved:

    netlink: avoid infinite retry looping in netlink_unicast() (CVE-2025-38727)

Tenable has extracted the preceding description block directly from the tested product 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 version of kernel installed on the remote host is prior to 5.4.296-217.428. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2025-108 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    dma-buf/dma-resv: check if the new fence is really later (CVE-2022-49935)

    In the Linux kernel, the following vulnerability has been resolved:

    fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var (CVE-2025-38215)

    In the Linux kernel, the following vulnerability has been resolved:

    netlink: avoid infinite retry looping in netlink_unicast() (CVE-2025-38727)

Tenable has extracted the preceding description block directly from the tested product 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 version of kernel installed on the remote host is prior to 5.10.240-238.966. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2025-103 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    dma-buf/dma-resv: check if the new fence is really later (CVE-2022-49935)

    In the Linux kernel, the following vulnerability has been resolved:

    cifs: fix small mempool leak in SMB2_negotiate() (CVE-2022-49938)

    In the Linux kernel, the following vulnerability has been resolved:

    mptcp: do not queue data on closed subflows (CVE-2022-50070)

    In the Linux kernel, the following vulnerability has been resolved:

    dma-buf: insert memory barrier before updating num_fences (CVE-2025-38095)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (CVE-2025-38162)

    In the Linux kernel, the following vulnerability has been resolved:

    fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var (CVE-2025-38215)

    In the Linux kernel, the following vulnerability has been resolved:

    netlink: avoid infinite retry looping in netlink_unicast() (CVE-2025-38727)

Tenable has extracted the preceding description block directly from the tested product 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 version of kernel installed on the remote host is prior to 4.14.355-280.672. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2025-2968 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    dma-buf/dma-resv: check if the new fence is really later (CVE-2022-49935)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/mlx5: Return the firmware result upon destroying QP/RQ (CVE-2023-53286)

    In the Linux kernel, the following vulnerability has been resolved:

    ftrace: Add cond_resched() to ftrace_graph_set_hash() (CVE-2025-37940)

    In the Linux kernel, the following vulnerability has been resolved:

    net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (CVE-2025-38061)

    In the Linux kernel, the following vulnerability has been resolved:

    net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction (CVE-2025-38161)

Tenable has extracted the preceding description block directly from the tested product 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv     object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to     explicit export/import that's not necessary the case any more. So without this check we would allow     userspace to force the kernel into an use after free error. Since the change is very small and defensive     it's probably a good idea to backport this to stable kernels as well just in case others are using the     dma_resv object in the same way. (CVE-2022-49935)

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

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

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


    The following security bugs were fixed:

    - CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
    - CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361     bsc#1226552).
    - CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
    - CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
    - CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain     (bsc#1222634).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices     (bsc#1235464).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
    - CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses     (bsc#1242782).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38060: bpf: abort verification if env->cur_state->loop_entry != NULL (bsc#1245155).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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	Name	Product	Family	Type	Severity
361530	CentOS Linux 8.4 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.4:CLSA-2025:1763731262)	Nessus	CentOS Local Security Checks	Local	high
352076	CentOS Linux 8.5 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.5:CLSA-2025:1763734783)	Nessus	CentOS Local Security Checks	Local	high
276730	Photon OS 4.0: Linux PHSA-2025-4.0-0913	Nessus	PhotonOS Local Security Checks	Local	high
261436	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2025-088 (ALASKERNEL-5.15-2025-088)	Nessus	Amazon Linux Local Security Checks	Local	high
261435	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2025-108 (ALASKERNEL-5.4-2025-108)	Nessus	Amazon Linux Local Security Checks	Local	high
261434	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2025-103 (ALASKERNEL-5.10-2025-103)	Nessus	Amazon Linux Local Security Checks	Local	high
252291	Amazon Linux 2 : kernel, --advisory ALAS2-2025-2968 (ALAS-2025-2968)	Nessus	Amazon Linux Local Security Checks	Local	high
247873	Linux Distros Unpatched Vulnerability : CVE-2022-49935	Nessus	Misc.	Local	high
241963	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:02264-1)	Nessus	SuSE Local Security Checks	Local	high

Detections

Analytics

CVE-2022-49935

high

Tenable Plugins

high

high

high

high

high

high

high

high

high