In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3GiB file. This should fail. echo echo "Try to fallocate a 3GiB file..." fallocate -l 3G $MNT/3G.file # Try to fallocate a 5GiB file. echo echo "Try to fallocate a 5GiB file..." fallocate -l 5G $MNT/5G.file # See we break the qgroup limit. echo sync btrfs qgroup show -r $MNT umount $MNT When running the test: $ ./qgroup-overflow.sh (...) Try to fallocate a 3GiB file... fallocate: fallocate failed: Disk quota exceeded Try to fallocate a 5GiB file... qgroupid rfer excl max_rfer -------- ---- ---- -------- 0/5 5.00GiB 5.00GiB 2.00GiB Since we have no control of how bytes_changed is used, it's better to set it to u64.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-990591 advisory.

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

    btrfs: fix qgroup reserve overflow the qgroup limit

    We use extent_changeset->bytes_changed in qgroup_reserve_data() to record     how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the     bytes_changed is set as unsigned int, and it will overflow if we try to     fallocate a range larger than 4GiB. The result is we reserve less bytes     and eventually break the qgroup limit.

    Unlike regular buffered/direct write, which we use one changeset for     each ordered extent, which can never be larger than 256M.  For     fallocate, we use one changeset for the whole range, thus it no longer     respects the 256M per extent limit, and caused the problem.

    The following example test script reproduces the problem:

      $ cat qgroup-overflow.sh       #!/bin/bash

      DEV=/dev/sdj       MNT=/mnt/sdj

      mkfs.btrfs -f $DEV       mount $DEV $MNT

      # Set qgroup limit to 2GiB.
      btrfs quota enable $MNT       btrfs qgroup limit 2G $MNT

      # Try to fallocate a 3GiB file. This should fail.
      echo       echo Try to fallocate a 3GiB file...
      fallocate -l 3G $MNT/3G.file

      # Try to fallocate a 5GiB file.
      echo       echo Try to fallocate a 5GiB file...
      fallocate -l 5G $MNT/5G.file

      # See we break the qgroup limit.
      echo       sync       btrfs qgroup show -r $MNT

      umount $MNT

    When running the test:

      $ ./qgroup-overflow.sh       (...)

      Try to fallocate a 3GiB file...
      fallocate: fallocate failed: Disk quota exceeded

      Try to fallocate a 5GiB file...

      qgroupid rfer excl max_rfer
      -------- ---- ---- --------       0/5 5.00GiB 5.00GiB 2.00GiB

    Since we have no control of how bytes_changed is used, it's better to     set it to u64.

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

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-988743 advisory.

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

    btrfs: fix qgroup reserve overflow the qgroup limit

    We use extent_changeset->bytes_changed in qgroup_reserve_data() to record     how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the     bytes_changed is set as unsigned int, and it will overflow if we try to     fallocate a range larger than 4GiB. The result is we reserve less bytes     and eventually break the qgroup limit.

    Unlike regular buffered/direct write, which we use one changeset for     each ordered extent, which can never be larger than 256M.  For     fallocate, we use one changeset for the whole range, thus it no longer     respects the 256M per extent limit, and caused the problem.

    The following example test script reproduces the problem:

      $ cat qgroup-overflow.sh       #!/bin/bash

      DEV=/dev/sdj       MNT=/mnt/sdj

      mkfs.btrfs -f $DEV       mount $DEV $MNT

      # Set qgroup limit to 2GiB.
      btrfs quota enable $MNT       btrfs qgroup limit 2G $MNT

      # Try to fallocate a 3GiB file. This should fail.
      echo       echo Try to fallocate a 3GiB file...
      fallocate -l 3G $MNT/3G.file

      # Try to fallocate a 5GiB file.
      echo       echo Try to fallocate a 5GiB file...
      fallocate -l 5G $MNT/5G.file

      # See we break the qgroup limit.
      echo       sync       btrfs qgroup show -r $MNT

      umount $MNT

    When running the test:

      $ ./qgroup-overflow.sh       (...)

      Try to fallocate a 3GiB file...
      fallocate: fallocate failed: Disk quota exceeded

      Try to fallocate a 5GiB file...

      qgroupid rfer excl max_rfer
      -------- ---- ---- --------       0/5 5.00GiB 5.00GiB 2.00GiB

    Since we have no control of how bytes_changed is used, it's better to     set it to u64.

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

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-990181 advisory.

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

    btrfs: fix qgroup reserve overflow the qgroup limit

    We use extent_changeset->bytes_changed in qgroup_reserve_data() to record     how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the     bytes_changed is set as unsigned int, and it will overflow if we try to     fallocate a range larger than 4GiB. The result is we reserve less bytes     and eventually break the qgroup limit.

    Unlike regular buffered/direct write, which we use one changeset for     each ordered extent, which can never be larger than 256M.  For     fallocate, we use one changeset for the whole range, thus it no longer     respects the 256M per extent limit, and caused the problem.

    The following example test script reproduces the problem:

      $ cat qgroup-overflow.sh       #!/bin/bash

      DEV=/dev/sdj       MNT=/mnt/sdj

      mkfs.btrfs -f $DEV       mount $DEV $MNT

      # Set qgroup limit to 2GiB.
      btrfs quota enable $MNT       btrfs qgroup limit 2G $MNT

      # Try to fallocate a 3GiB file. This should fail.
      echo       echo Try to fallocate a 3GiB file...
      fallocate -l 3G $MNT/3G.file

      # Try to fallocate a 5GiB file.
      echo       echo Try to fallocate a 5GiB file...
      fallocate -l 5G $MNT/5G.file

      # See we break the qgroup limit.
      echo       sync       btrfs qgroup show -r $MNT

      umount $MNT

    When running the test:

      $ ./qgroup-overflow.sh       (...)

      Try to fallocate a 3GiB file...
      fallocate: fallocate failed: Disk quota exceeded

      Try to fallocate a 5GiB file...

      qgroupid rfer excl max_rfer
      -------- ---- ---- --------       0/5 5.00GiB 5.00GiB 2.00GiB

    Since we have no control of how bytes_changed is used, it's better to     set it to u64.

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

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-987527 advisory.

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

    btrfs: fix qgroup reserve overflow the qgroup limit

    We use extent_changeset->bytes_changed in qgroup_reserve_data() to record     how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the     bytes_changed is set as unsigned int, and it will overflow if we try to     fallocate a range larger than 4GiB. The result is we reserve less bytes     and eventually break the qgroup limit.

    Unlike regular buffered/direct write, which we use one changeset for     each ordered extent, which can never be larger than 256M.  For     fallocate, we use one changeset for the whole range, thus it no longer     respects the 256M per extent limit, and caused the problem.

    The following example test script reproduces the problem:

      $ cat qgroup-overflow.sh       #!/bin/bash

      DEV=/dev/sdj       MNT=/mnt/sdj

      mkfs.btrfs -f $DEV       mount $DEV $MNT

      # Set qgroup limit to 2GiB.
      btrfs quota enable $MNT       btrfs qgroup limit 2G $MNT

      # Try to fallocate a 3GiB file. This should fail.
      echo       echo Try to fallocate a 3GiB file...
      fallocate -l 3G $MNT/3G.file

      # Try to fallocate a 5GiB file.
      echo       echo Try to fallocate a 5GiB file...
      fallocate -l 5G $MNT/5G.file

      # See we break the qgroup limit.
      echo       sync       btrfs qgroup show -r $MNT

      umount $MNT

    When running the test:

      $ ./qgroup-overflow.sh       (...)

      Try to fallocate a 3GiB file...
      fallocate: fallocate failed: Disk quota exceeded

      Try to fallocate a 5GiB file...

      qgroupid rfer excl max_rfer
      -------- ---- ---- --------       0/5 5.00GiB 5.00GiB 2.00GiB

    Since we have no control of how bytes_changed is used, it's better to     set it to u64.

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

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

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

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

    The following security bugs were fixed:

    - CVE-2021-46925: Fixed kernel panic caused by race of smc_sock (bsc#1220466).
    - CVE-2021-47645: media: staging: media: zoran: calculate the right buffer number for zoran_reap_stat_com     (bsc#1237767).
    - CVE-2021-47648: gpu: host1x: Fix a memory leak in 'host1x_remove()' (bsc#1237725).
    - CVE-2022-49046: i2c: dev: check return value when calling dev_set_name() (bsc#1237842).
    - CVE-2022-49051: net: usb: aqc111: Fix out-of-bounds accesses in RX fixup (bsc#1237903).
    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49059: nfc: nci: add flush_workqueue to prevent uaf (bsc#1238007).
    - CVE-2022-49074: irqchip/gic-v3: Fix GICR_CTLR.RWP polling (bsc#1237728).
    - CVE-2022-49075: btrfs: fix qgroup reserve overflow the qgroup limit (bsc#1237733).
    - CVE-2022-49084: qede: confirm skb is allocated before using (bsc#1237751).
    - CVE-2022-49107: ceph: fix memory leak in ceph_readdir when note_last_dentry returns error (bsc#1237973).
    - CVE-2022-49109: ceph: fix inode reference leakage in ceph_get_snapdir() (bsc#1237836).
    - CVE-2022-49119: scsi: pm8001: Fix memory leak in pm8001_chip_fw_flash_update_req() (bsc#1237925).
    - CVE-2022-49120: scsi: pm8001: Fix task leak in pm8001_send_abort_all() (bsc#1237969).
    - CVE-2022-49209: bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full (bsc#1238252).
    - CVE-2022-49220: dax: make sure inodes are flushed before destroy cache (bsc#1237936).
    - CVE-2022-49275: can: m_can: m_can_tx_handler(): fix use after free of skb (bsc#1238719).
    - CVE-2022-49286: tpm: use try_get_ops() in tpm-space.c (bsc#1238647).
    - CVE-2022-49292: ALSA: oss: Fix PCM OSS buffer allocation overflow (bsc#1238625).
    - CVE-2022-49308: extcon: Modify extcon device to be created after driver data is set (bsc#1238654).
    - CVE-2022-49331: nfc: st21nfca: fix memory leaks in EVT_TRANSACTION handling (bsc#1237813).
    - CVE-2022-49344: af_unix: Fix a data-race in unix_dgram_peer_wake_me() (bsc#1237988).
    - CVE-2022-49367: net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register (bsc#1238447).
    - CVE-2022-49370: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle (bsc#1238467).
    - CVE-2022-49372: tcp: tcp_rtx_synack() can be called from process context (bsc#1238251).
    - CVE-2022-49388: ubi: ubi_create_volume: Fix use-after-free when volume creation failed (bsc#1237934).
    - CVE-2022-49395: um: Fix out-of-bounds read in LDT setup (bsc#1237953).
    - CVE-2022-49397: phy: qcom-qmp: fix struct clk leak on probe errors (bsc#1237823).
    - CVE-2022-49404: RDMA/hfi1: Fix potential integer multiplication overflow errors (bsc#1238430).
    - CVE-2022-49416: wifi: mac80211: fix use-after-free in chanctx code (bsc#1238293).
    - CVE-2022-49433: RDMA/hfi1: Prevent use of lock before it is initialized (bsc#1238268).
    - CVE-2022-49472: net: phy: micrel: Allow probing without .driver_data (bsc#1238951).
    - CVE-2022-49488: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock (bsc#1238600).
    - CVE-2022-49495: drm/msm/hdmi: check return value after calling platform_get_resource_byname()     (bsc#1237932).
    - CVE-2022-49497: net: remove two BUG() from skb_checksum_help() (bsc#1238946).
    - CVE-2022-49505: NFC: NULL out the dev->rfkill to prevent UAF (bsc#1238615).
    - CVE-2022-49516: ice: always check VF VSI pointer values (bsc#1238953).
    - CVE-2022-49519: ath10k: skip ath10k_halt during suspend for driver state RESTARTING (bsc#1238943).
    - CVE-2022-49524: media: pci: cx23885: Fix the error handling in cx23885_initdev() (bsc#1238949).
    - CVE-2022-49530: drm/amd/pm: fix double free in si_parse_power_table() (bsc#1238944).
    - CVE-2022-49538: ALSA: jack: Fix mutex call in snd_jack_report() (bsc#1238843).
    - CVE-2022-49544: ipw2x00: Fix potential NULL dereference in libipw_xmit() (bsc#1238721).
    - CVE-2022-49545: ALSA: usb-audio: Cancel pending work at closing a MIDI substream (bsc#1238729).
    - CVE-2022-49546: x86/kexec: Fix double-free of elf header buffer (bsc#1238750).
    - CVE-2022-49563: crypto: qat - add param check for RSA (bsc#1238787).
    - CVE-2022-49564: crypto: qat - add param check for DH (bsc#1238789).
    - CVE-2022-49578: ip: Fix data-races around sysctl_ip_prot_sock. (bsc#1238794).
    - CVE-2022-49581: be2net: Fix buffer overflow in be_get_module_eeprom (bsc#1238540).
    - CVE-2022-49589: kABI: protect mr_ifc_count change (bsc#1238598).
    - CVE-2022-49605: igc: Reinstate IGC_REMOVED logic and implement it properly (bsc#1238433).
    - CVE-2022-49607: perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()     (bsc#1238817).
    - CVE-2022-49610: KVM: VMX: Prevent RSB underflow before vmenter (bsc#1238952).
    - CVE-2022-49619: net: sfp: fix memory leak in sfp_probe() (bsc#1239003).
    - CVE-2022-49620: net: tipc: fix possible refcount leak in tipc_sk_create() (bsc#1239002).
    - CVE-2022-49640: sysctl: Fix data races in proc_douintvec_minmax() (bsc#1237782).
    - CVE-2022-49641: sysctl: Fix data races in proc_douintvec() (bsc#1237831).
    - CVE-2022-49667: net: bonding: fix use-after-free after 802.3ad slave unbind (bsc#1238282).
    - CVE-2022-49672: net: tun: unlink NAPI from device on destruction (bsc#1238816).
    - CVE-2022-49711: bus: fsl-mc-bus: fix KASAN use-after-free in fsl_mc_bus_remove() (bsc#1238416).
    - CVE-2022-49727: ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg (bsc#1239059).
    - CVE-2022-49740: wifi: brcmfmac: Check the count value of channel spec to prevent out-of-bounds reads     (bsc#1240233).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2023-52997: ipv4: prevent potential spectre v1 gadget in ip_metrics_convert() (bsc#1240303).
    - CVE-2023-53010: bnxt: Do not read past the end of test names (bsc#1240290).
    - CVE-2023-53019: net: mdio: validate parameter addr in mdiobus_get_phy() (bsc#1240286).
    - CVE-2024-35910: kABI fix for tcp: properly terminate timers for kernel sockets (bsc#1224489).
    - CVE-2024-36968: Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init() (bsc#1226130).
    - CVE-2024-38559: scsi: qedf: Ensure the copied buf is NUL terminated (bsc#1226785).
    - CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
    - CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg     (bsc#1235733).
    - CVE-2024-49935: ACPI: PAD: fix crash in exit_round_robin() (bsc#1232370).
    - CVE-2024-49940: l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
    - CVE-2024-50269: usb: musb: sunxi: Fix accessing an released usb phy (bsc#1233458).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
    - CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
    - CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
    - CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
    - CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
    - CVE-2024-57973: rdma/cxgb4: Prevent potential integer overflow on 32bit (bsc#1238531).
    - CVE-2024-57979: kABI workaround for pps changes (bsc#1238521).
    - 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-2024-58052: drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table     (bsc#1238986).
    - CVE-2024-58071: team: prevent adding a device which is already a team device lower (bsc#1238970)
    - CVE-2024-58072: wifi: rtlwifi: remove unused check_buddy_priv (bsc#1238964).
    - CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21708: net: usb: rtl8150: enable basic endpoint checking (bsc#1239087).
    - CVE-2025-21744: wifi: brcmfmac: fix NULL pointer dereference in brcmf_txfinalize() (bsc#1238903).
    - CVE-2025-21759: ipv6: mcast: extend RCU protection in igmp6_send() (bsc#1238738).
    - CVE-2025-21760: ndisc: extend RCU protection in ndisc_send_skb() (bsc#1238763).
    - CVE-2025-21762: arp: use RCU protection in arp_xmit() (bsc#1238780).
    - CVE-2025-21763: neighbour: use RCU protection in __neigh_notify() (bsc#1237897).
    - CVE-2025-21765: ipv6: use RCU protection in ip6_default_advmss() (bsc#1237906).
    - CVE-2025-21766: ipv4: use RCU protection in __ip_rt_update_pmtu() (bsc#1238754).
    - CVE-2025-21776: USB: hub: Ignore non-compliant devices with too many configs or interfaces     (bsc#1238909).
    - CVE-2025-21782: orangefs: fix a oob in orangefs_debug_write (bsc#1239117).
    - CVE-2025-21785: arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array (bsc#1238747).
    - CVE-2025-21791: vrf: use RCU protection in l3mdev_l3_out() (bsc#1238512).
    - CVE-2025-21796: nfsd: clear acl_access/acl_default after releasing them (bsc#1238716).
    - CVE-2025-21802: net: hns3: fix oops when unload drivers paralleling (bsc#1238751).
    - CVE-2025-21821: fbdev: omap: use threaded IRQ for LCD DMA (bsc#1239174).
    - CVE-2025-21831: PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (bsc#1239039).
    - CVE-2025-21846: acct: perform last write from workqueue (bsc#1239508).
    - CVE-2025-21848: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (bsc#1239479).
    - CVE-2025-21865: gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl() (bsc#1239481).
    - CVE-2025-21871: tee: optee: Fix supplicant wait loop (bsc#1240183).
    - CVE-2025-21877: usbnet: gl620a: fix endpoint checking in genelink_bind() (bsc#1240172).
    - CVE-2025-21891: ipvlan: ensure network headers are in skb linear part (bsc#1240186).
    - CVE-2025-21916: usb: atm: cxacru: fix a flaw in existing endpoint checks (bsc#1240582).
    - CVE-2025-21922: ppp: Fix KMSAN uninit-value warning with bpf (bsc#1240639).
    - CVE-2025-21934: rapidio: fix an API misues when rio_add_net() fails (bsc#1240708).
    - CVE-2025-21935: rapidio: add check for rio_add_net() in rio_scan_alloc_net() (bsc#1240700).
    - CVE-2025-21969: Bluetooth: L2CAP: Fix build errors in some archs (bsc#1240784).
    - CVE-2025-21993: iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic() (bsc#1240797).
    - CVE-2025-21996: drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse() (bsc#1240801).
    - CVE-2025-22007: Bluetooth: Fix error code in chan_alloc_skb_cb() (bsc#1240582).


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.

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.

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

  - btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in     qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the     bytes_changed is set as unsigned int, and it will overflow if we try to fallocate a range larger than     4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular     buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than     256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per     extent limit, and caused the problem. The following example test script reproduces the problem: $ cat     qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup     limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3GiB file. This     should fail. echo echo Try to fallocate a 3GiB file... fallocate -l 3G $MNT/3G.file # Try to fallocate a     5GiB file. echo echo Try to fallocate a 5GiB file... fallocate -l 5G $MNT/5G.file # See we break the     qgroup limit. echo sync btrfs qgroup show -r $MNT umount $MNT When running the test: $ ./qgroup-     overflow.sh (...) Try to fallocate a 3GiB file... fallocate: fallocate failed: Disk quota exceeded Try to     fallocate a 5GiB file... qgroupid rfer excl max_rfer -------- ---- ---- -------- 0/5 5.00GiB 5.00GiB     2.00GiB Since we have no control of how bytes_changed is used, it's better to set it to u64.
    (CVE-2022-49075)

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

The version of kernel installed on the remote host is prior to 5.4.190-107.353. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2024-076 advisory.

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

    ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl (CVE-2021-47634)

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

    Revert Revert block, bfq: honor already-setup queue merges (CVE-2021-47646)

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

    ASoC: soc-compress: prevent the potentially use of null pointer (CVE-2021-47650)

    When the KVM updates the guest's page table entry, it will first use get_user_pages_fast() to pin the     page, and when it fails (e.g. the vma->flags has VM_IO or VM_PFNMAP), it will get corresponding VMA where     the page lies in through find_vma_intersection(), calculate the physical address, and map the page to the     kernel virtual address through memremap(), and finally, write the update.The problem is that when we get     the vma through find_vma_intersection(), only VM_PFNMAP is checked, not both VM_IO and VM_PFNMAP. In the     reproducer below, after the KVM_SET_USER_MEMORY_REGION is completed, we replace the guest's memory mapping     with the kernel-user shared region of io_uring and then perform the KVM_TRANSLATE operation, which finally     triggers the page table entry update. Now, memremap() will return page_offset_base (direct mapping of all     physical memory) + vaddr (the linear address of KVM_TRANSLATE) + vm_pgoff (the offset when io_uring     performs mmap(2)), and use the return value as the base address for CMPXCHG (write 0x21 in this case).
    Since both vaddr and vm_pgoff are controllable by the user-mode process, writing may exceed the previously     mapped guest memory space and trigger exceptions such as UAF. The vulnerability shares similarities with     CVE-2021-22543. (CVE-2022-1158)

    A vulnerability was found in the pfkey_register function in net/key/af_key.c in the Linux kernel. This     flaw allows a local, unprivileged user to gain access to kernel memory, leading to a system crash or a     leak of internal kernel information. (CVE-2022-1353)

    A flaw was found in the Linux kernel implementation of proxied virtualized TPM devices. On a system where     virtualized TPM devices are configured (this is not the default) a local attacker can create a use-after-     free and create a situation where it may be possible to escalate privileges on the system. (CVE-2022-2977)

    A flaw was found in the Linux kernel. A NULL pointer dereference may occur while a slip driver is in     progress to detach in sl_tx_timeout in drivers/net/slip/slip.c. This issue could allow an attacker to     crash the system or leak internal kernel information. (CVE-2022-41858)

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

    swiotlb: fix info leak with DMA_FROM_DEVICE (CVE-2022-48853)

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

    dm integrity: fix memory corruption when tag_size is less than digest size (CVE-2022-49044)

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

    ipv6: fix panic when forwarding a pkt with no in6 dev (CVE-2022-49048)

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

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

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

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

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

    veth: Ensure eth header is in skb's linear part (CVE-2022-49066)

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

    ata: sata_dwc_460ex: Fix crash due to OOB write (CVE-2022-49073)

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

    irqchip/gic-v3: Fix GICR_CTLR.RWP polling (CVE-2022-49074)

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

    btrfs: fix qgroup reserve overflow the qgroup limit (CVE-2022-49075)

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

    mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0) (CVE-2022-49077)

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

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

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

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

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

    qede: confirm skb is allocated before using (CVE-2022-49084)

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

    drbd: Fix five use after free bugs in get_initial_state (CVE-2022-49085)

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

    rxrpc: fix a race in rxrpc_exit_net() (CVE-2022-49087)

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

    net: ipv4: fix route with nexthop object delete warning (CVE-2022-49092)

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

    net/tls: fix slab-out-of-bounds bug in decrypt_internal (CVE-2022-49094)

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

    Drivers: hv: vmbus: Fix potential crash on module unload (CVE-2022-49098)

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

    virtio_console: eliminate anonymous module_init & module_exit (CVE-2022-49100)

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

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

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

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

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

    ACPI: CPPC: Avoid out of bounds access when parsing _CPC data (CVE-2022-49145)

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

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

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

    ntfs: add sanity check on allocation size (CVE-2022-49166)

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

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

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

    PM: core: keep irq flags in device_pm_check_callbacks() (CVE-2022-49175)

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

    bfq: fix use-after-free in bfq_dispatch_request (CVE-2022-49176)

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

    block, bfq: don't move oom_bfqq (CVE-2022-49179)

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

    LSM: general protection fault in legacy_parse_param (CVE-2022-49180)

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

    af_netlink: Fix shift out of bounds in group mask calculation (CVE-2022-49197)

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

    bpf, sockmap: Fix more uncharged while msg has more_data (CVE-2022-49204)

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

    bpf, sockmap: Fix double uncharge the mem of sk_msg (CVE-2022-49205)

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

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

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

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

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

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

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

    power: supply: ab8500: Fix memory leak in ab8500_fg_sysfs_init (CVE-2022-49224)

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

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

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

    NFSD: prevent integer overflow on 32 bit systems (CVE-2022-49279)

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

    NFSD: prevent underflow in nfssvc_decode_writeargs() (CVE-2022-49280)

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

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

    A flaw that boot CPU could be vulnerable for the speculative execution behavior kind of attacks in the     Linux kernel X86 CPU Power management options functionality was found in the way user resuming CPU from     suspend-to-RAM. A local user could use this flaw to potentially get unauthorized access to some memory of     the CPU similar to the speculative execution behavior kind of attacks. (CVE-2023-1637)

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.276-211.499. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2024-2569 advisory.

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

    ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl (CVE-2021-47634)

    A use-after-free flaw was found in the Linux kernel's FUSE filesystem in the way a user triggers write().
    This flaw allows a local user to gain unauthorized access to data from the FUSE filesystem, resulting in     privilege escalation. (CVE-2022-1011)

    A vulnerability was found in the pfkey_register function in net/key/af_key.c in the Linux kernel. This     flaw allows a local, unprivileged user to gain access to kernel memory, leading to a system crash or a     leak of internal kernel information. (CVE-2022-1353)

    A flaw was found in the Linux kernel implementation of proxied virtualized TPM devices. On a system where     virtualized TPM devices are configured (this is not the default) a local attacker can create a use-after-     free and create a situation where it may be possible to escalate privileges on the system. (CVE-2022-2977)

    A flaw was found in the Linux kernel. A NULL pointer dereference may occur while a slip driver is in     progress to detach in sl_tx_timeout in drivers/net/slip/slip.c. This issue could allow an attacker to     crash the system or leak internal kernel information. (CVE-2022-41858)

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

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

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

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

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

    veth: Ensure eth header is in skb's linear part (CVE-2022-49066)

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

    btrfs: fix qgroup reserve overflow the qgroup limit (CVE-2022-49075)

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

    mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0) (CVE-2022-49077)

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

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

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

    drbd: Fix five use after free bugs in get_initial_state (CVE-2022-49085)

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

    virtio_console: eliminate anonymous module_init & module_exit (CVE-2022-49100)

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

    Bluetooth: Fix use after free in hci_send_acl (CVE-2022-49111)

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

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

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

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

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

    ACPI: CPPC: Avoid out of bounds access when parsing _CPC data (CVE-2022-49145)

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

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

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

    ntfs: add sanity check on allocation size (CVE-2022-49166)

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

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

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

    PM: core: keep irq flags in device_pm_check_callbacks() (CVE-2022-49175)

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

    af_netlink: Fix shift out of bounds in group mask calculation (CVE-2022-49197)

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

    power: supply: ab8500: Fix memory leak in ab8500_fg_sysfs_init (CVE-2022-49224)

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

    NFSD: prevent underflow in nfssvc_decode_writeargs() (CVE-2022-49280)

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

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

    A flaw that boot CPU could be vulnerable for the speculative execution behavior kind of attacks in the     Linux kernel X86 CPU Power management options functionality was found in the way user resuming CPU from     suspend-to-RAM. A local user could use this flaw to potentially get unauthorized access to some memory of     the CPU similar to the speculative execution behavior kind of attacks. (CVE-2023-1637)

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.112-108.499. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2023-036 advisory.

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

    ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl (CVE-2021-47634)

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

    Revert Revert block, bfq: honor already-setup queue merges (CVE-2021-47646)

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

    ASoC: soc-compress: prevent the potentially use of null pointer (CVE-2021-47650)

    A denial of service (DOS) issue was found in the Linux kernel's smb2_ioctl_query_info function in     the fs/cifs/smb2ops.c Common Internet File System (CIFS) due to an incorrect return from the memdup_user     function. This flaw allows a local, privileged (CAP_SYS_ADMIN) attacker to crash the system.
    (CVE-2022-0168)

    When the KVM updates the guest's page table entry, it will first use get_user_pages_fast() to pin the     page, and when it fails (e.g. the vma->flags has VM_IO or VM_PFNMAP), it will get corresponding VMA where     the page lies in through find_vma_intersection(), calculate the physical address, and map the page to the     kernel virtual address through memremap(), and finally, write the update.The problem is that when we get     the vma through find_vma_intersection(), only VM_PFNMAP is checked, not both VM_IO and VM_PFNMAP. In the     reproducer below, after the KVM_SET_USER_MEMORY_REGION is completed, we replace the guest's memory mapping     with the kernel-user shared region of io_uring and then perform the KVM_TRANSLATE operation, which finally     triggers the page table entry update. Now, memremap() will return page_offset_base (direct mapping of all     physical memory) + vaddr (the linear address of KVM_TRANSLATE) + vm_pgoff (the offset when io_uring     performs mmap(2)), and use the return value as the base address for CMPXCHG (write 0x21 in this case).
    Since both vaddr and vm_pgoff are controllable by the user-mode process, writing may exceed the previously     mapped guest memory space and trigger exceptions such as UAF. The vulnerability shares similarities with     CVE-2021-22543. (CVE-2022-1158)

    A vulnerability was found in the pfkey_register function in net/key/af_key.c in the Linux kernel. This     flaw allows a local, unprivileged user to gain access to kernel memory, leading to a system crash or a     leak of internal kernel information. (CVE-2022-1353)

    A use-after-free flaw was found in the Linux kernel's io_uring interface subsystem in the way a user     triggers a race condition between timeout flush and removal. This flaw allows a local user to crash or     escalate their privileges on the system. (CVE-2022-29582)

    A flaw was found in the Linux kernel implementation of proxied virtualized TPM devices. On a system where     virtualized TPM devices are configured (this is not the default) a local attacker can create a use-after-     free and create a situation where it may be possible to escalate privileges on the system. (CVE-2022-2977)

    A flaw was found in the Linux kernel. A NULL pointer dereference may occur while a slip driver is in     progress to detach in sl_tx_timeout in drivers/net/slip/slip.c. This issue could allow an attacker to     crash the system or leak internal kernel information. (CVE-2022-41858)

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

    swiotlb: fix info leak with DMA_FROM_DEVICE (CVE-2022-48853)

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

    dm integrity: fix memory corruption when tag_size is less than digest size (CVE-2022-49044)

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

    ipv6: fix panic when forwarding a pkt with no in6 dev (CVE-2022-49048)

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

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

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

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

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

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

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

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

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

    veth: Ensure eth header is in skb's linear part (CVE-2022-49066)

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

    gpio: Restrict usage of GPIO chip irq members before initialization (CVE-2022-49072)

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

    ata: sata_dwc_460ex: Fix crash due to OOB write (CVE-2022-49073)

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

    irqchip/gic-v3: Fix GICR_CTLR.RWP polling (CVE-2022-49074)

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

    btrfs: fix qgroup reserve overflow the qgroup limit (CVE-2022-49075)

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

    mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0) (CVE-2022-49077)

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

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

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

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

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

    qede: confirm skb is allocated before using (CVE-2022-49084)

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

    drbd: Fix five use after free bugs in get_initial_state (CVE-2022-49085)

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

    net: openvswitch: fix leak of nested actions (CVE-2022-49086)

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

    rxrpc: fix a race in rxrpc_exit_net() (CVE-2022-49087)

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

    net: ipv4: fix route with nexthop object delete warning (CVE-2022-49092)

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

    net/tls: fix slab-out-of-bounds bug in decrypt_internal (CVE-2022-49094)

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

    NFS: Avoid writeback threads getting stuck in mempool_alloc() (CVE-2022-49097)

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

    Drivers: hv: vmbus: Fix potential crash on module unload (CVE-2022-49098)

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

    virtio_console: eliminate anonymous module_init & module_exit (CVE-2022-49100)

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

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

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

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

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

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

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

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

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

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

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

    ACPI: CPPC: Avoid out of bounds access when parsing _CPC data (CVE-2022-49145)

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

    watch_queue: Free the page array when watch_queue is dismantled (CVE-2022-49148)

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

    rxrpc: Fix call timer start racing with call destruction (CVE-2022-49149)

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

    wireguard: socket: free skb in send6 when ipv6 is disabled (CVE-2022-49153)

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

    KVM: SVM: fix panic on out-of-bounds guest IRQ (CVE-2022-49154)

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

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

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

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

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

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

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

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

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

    PM: core: keep irq flags in device_pm_check_callbacks() (CVE-2022-49175)

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

    bfq: fix use-after-free in bfq_dispatch_request (CVE-2022-49176)

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

    block, bfq: don't move oom_bfqq (CVE-2022-49179)

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

    LSM: general protection fault in legacy_parse_param (CVE-2022-49180)

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

    af_netlink: Fix shift out of bounds in group mask calculation (CVE-2022-49197)

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

    bpf, sockmap: Fix more uncharged while msg has more_data (CVE-2022-49204)

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

    bpf, sockmap: Fix double uncharge the mem of sk_msg (CVE-2022-49205)

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

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

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

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

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

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

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

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

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

    power: supply: ab8500: Fix memory leak in ab8500_fg_sysfs_init (CVE-2022-49224)

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

    watch_queue: Actually free the watch (CVE-2022-49256)

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

    watch_queue: Fix NULL dereference in error cleanup (CVE-2022-49257)

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

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

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

    drm/i915/gem: add missing boundary check in vm_access (CVE-2022-49261)

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

    exec: Force single empty string when argv is empty (CVE-2022-49264)

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

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

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

    ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock (CVE-2022-49272)

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

    NFSD: prevent integer overflow on 32 bit systems (CVE-2022-49279)

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

    NFSD: prevent underflow in nfssvc_decode_writeargs() (CVE-2022-49280)

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

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

    A use-after-free flaw was found in the Linux kernel's core dump subsystem. This flaw could allow a local     user to crash the system. (CVE-2023-1249)

    A flaw that boot CPU could be vulnerable for the speculative execution behavior kind of attacks in the     Linux kernel X86 CPU Power management options functionality was found in the way user resuming CPU from     suspend-to-RAM. A local user could use this flaw to potentially get unauthorized access to some memory of     the CPU similar to the speculative execution behavior kind of attacks. (CVE-2023-1637)

    Improper restriction of operations within the bounds of a memory buffer in some Intel(R) i915 Graphics     drivers for linux before kernel version 6.2.10 may allow an authenticated user to potentially enable     escalation of privilege via local access. (CVE-2023-28410)

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.

ID	Name	Product	Family	Severity
274241	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-990591)	Nessus	Unity Linux Local Security Checks	medium
273209	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988743)	Nessus	Unity Linux Local Security Checks	medium
272588	Unity Linux 20.1050e Security Update: kernel (UTSA-2025-990181)	Nessus	Unity Linux Local Security Checks	medium
271090	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987527)	Nessus	Unity Linux Local Security Checks	medium
234545	SUSE SLES12 Security Update : kernel (SUSE-SU-2025:1293-1)	Nessus	SuSE Local Security Checks	high
234407	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	high
225655	Linux Distros Unpatched Vulnerability : CVE-2022-49075	Nessus	Misc.	medium
206247	Amazon Linux 2 : kernel (ALASKERNEL-5.4-2024-076)	Nessus	Amazon Linux Local Security Checks	high
200382	Amazon Linux 2 : kernel (ALAS-2024-2569)	Nessus	Amazon Linux Local Security Checks	high
180564	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2023-036)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2022-49075

medium

Tenable Plugins

medium

medium

medium

medium

high

high

medium

high

high

high