In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Don't enable interrupts in its_irq_set_vcpu_affinity() The following call-chain leads to enabling interrupts in a nested interrupt disabled section: irq_set_vcpu_affinity() irq_get_desc_lock() raw_spin_lock_irqsave() <--- Disable interrupts its_irq_set_vcpu_affinity() guard(raw_spinlock_irq) <--- Enables interrupts when leaving the guard() irq_put_desc_unlock() <--- Warns because interrupts are enabled This was broken in commit b97e8a2f7130, which replaced the original raw_spin_[un]lock() pair with guard(raw_spinlock_irq). Fix the issue by using guard(raw_spinlock). [ tglx: Massaged change log ]

The remote NewStart CGSL host, running version MAIN 7.02, has kernel packages installed that are affected by multiple vulnerabilities:

  - In the Linux kernel, the following vulnerability has been resolved: smack: tcp: ipv4, fix incorrect     labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects     to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets     are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to     write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack     in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule     'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a     program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener     at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data     in both directions. * Collect network traffic of this connection. All packets in both directions are     labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized,     and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This     behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no     explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the     Smack documentation claims. (CVE-2024-47659)

  - In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: Fix kernel crash     on receiver USB disconnect hidpp_connect_event() has *four* time-of-check vs time-of-use (TOCTOU) races     when it races with itself. hidpp_connect_event() primarily runs from a workqueue but it also runs on     probe() and if a device-connected packet is received by the hw when the thread running     hidpp_connect_event() from probe() is waiting on the hw, then a second thread running     hidpp_connect_event() will be started from the workqueue. This opens the following races (note the below     code is simplified): 1. Retrieving + printing the protocol (harmless race): if (!hidpp->protocol_major) {     hidpp_root_get_protocol_version() hidpp->protocol_major = response.rap.params[0]; } We can actually see     this race hit in the dmesg in the abrt output attached to rhbz#2227968: [ 3064.624215] logitech-hidpp-     device 0003:046D:4071.0049: HID++ 4.5 device connected. [ 3064.658184] logitech-hidpp-device     0003:046D:4071.0049: HID++ 4.5 device connected. Testing with extra logging added has shown that after     this the 2 threads take turn grabbing the hw access mutex (send_mutex) so they ping-pong through all the     other TOCTOU cases managing to hit all of them: 2. Updating the name to the HIDPP name (harmless race): if     (hidpp->name == hdev->name) { ... hidpp->name = new_name; } 3. Initializing the power_supply class for the     battery (problematic!): hidpp_initialize_battery() { if (hidpp->battery.ps) return 0; probe_battery(); /*     Blocks, threads take turns executing this */ hidpp->battery.desc.properties = devm_kmemdup(dev,     hidpp_battery_props, cnt, GFP_KERNEL); hidpp->battery.ps =     devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); } 4. Creating delayed     input_device (potentially problematic): if (hidpp->delayed_input) return; hidpp->delayed_input =     hidpp_allocate_input(hdev); The really big problem here is 3. Hitting the race leads to the following     sequence: hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL);
    hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); ...
    hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL);
    hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); So now we     have registered 2 power supplies for the same battery, which looks a bit weird from userspace's pov but     this is not even the really big problem. Notice how: 1. This is all devm-maganaged 2. The     hidpp->battery.desc struct is shared between the 2 power supplies 3. hidpp->battery.desc.properties points     to the result from the second devm_kmemdup() This causes a use after free scenario on USB disconnect of     the receiver: 1. The last registered power supply class device gets unregistered 2. The memory from the     last devm_kmemdup() call gets freed, hidpp->battery.desc.properties now points to freed memory 3. The     first registered power supply class device gets unregistered, this involves sending a remove uevent to     userspace which invokes power_supply_uevent() to fill the uevent data 4. power_supply_uevent() uses     hidpp->battery.desc.properties which now points to freed memory leading to backtraces like this one: Sep     22 20:01:35 eric kernel: BUG: unable to handle page fault for address: ffffb2140e017f08 ... Sep 22     20:01:35 eric kernel: Workqueue: usb_hub_wq hub_event Sep 22 20:01:35 eric kernel: RIP:
    0010:power_supply_uevent+0xee/0x1d0 ... Sep 22 20:01:35 eric kernel: ? asm_exc_page_fault+0x26/0x30 Sep 22     20:01:35 eric kernel: ? power_supply_uevent+0xee/0x1d0 Sep 22 20:01:35 eric kernel: ?     power_supply_uevent+0x10d/0x1d0 Sep 22 20:01:35 eric kernel: dev_uevent+0x10f/0x2d0 Sep 22 20:01:35 eric     kernel: kobject_uevent_env+0x291/0x680 Sep 22 20:01:35 eric kernel: ---truncated--- (CVE-2023-52478)

  - In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h6: Reparent CPUX     during PLL CPUX rate change While PLL CPUX clock rate change when CPU is running from it works in vast     majority of cases, now and then it causes instability. This leads to system crashes and other undefined     behaviour. After a lot of testing (30+ hours) while also doing a lot of frequency switches, we can't     observe any instability issues anymore when doing reparenting to stable clock like 24 MHz oscillator.
    (CVE-2023-52882)

  - In the Linux kernel, the following vulnerability has been resolved: net: can: j1939: enhanced error     handling for tightly received RTS messages in xtp_rx_rts_session_new This patch enhances error handling in     scenarios with RTS (Request to Send) messages arriving closely. It replaces the less informative     WARN_ON_ONCE backtraces with a new error handling method. This provides clearer error messages and allows     for the early termination of problematic sessions. Previously, sessions were only released at the end of     j1939_xtp_rx_rts(). Potentially this could be reproduced with something like: testj1939 -r vcan0:0x80 &     while true; do # send first RTS cansend vcan0 18EC8090#1014000303002301; # send second RTS cansend vcan0     18EC8090#1014000303002301; # send abort cansend vcan0 18EC8090#ff00000000002301; done (CVE-2023-52887)

  - In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Only free     buffer VA that is not NULL In the MediaTek vcodec driver, while mtk_vcodec_mem_free() is mostly called     only when the buffer to free exists, there are some instances that didn't do the check and triggered     warnings in practice. We believe those checks were forgotten unintentionally. Add the checks back to fix     the warnings. (CVE-2023-52888)

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

The remote Ubuntu 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7653-1 advisory.

    It was discovered that the CIFS network file system implementation in the Linux kernel did not properly     verify the target namespace when handling upcalls. An attacker could use this to expose sensitive     information. (CVE-2025-2312)

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - PowerPC architecture;

    - S390 architecture;

    - Block layer subsystem;

    - Serial ATA and Parallel ATA drivers;

    - Drivers core;

    - Network block device driver;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - FireWire subsystem;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - Media drivers;

    - NVIDIA Tegra memory controller driver;

    - Fastrpc Driver;

    - Network drivers;

    - Mellanox network drivers;

    - Operating Performance Points (OPP) driver;

    - PCI subsystem;

    - x86 platform drivers;

    - i.MX PM domains;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - Remote Processor subsystem;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - Media staging drivers;

    - TTY drivers;

    - UFS subsystem;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Serial drivers;

    - AFS file system;

    - File systems infrastructure;

    - BTRFS file system;

    - F2FS file system;

    - GFS2 file system;

    - NILFS2 file system;

    - File system notification infrastructure;

    - Overlay file system;

    - Proc file system;

    - SMB network file system;

    - UBI file system;

    - Timer subsystem;

    - KVM subsystem;

    - Networking core;

    - ptr_ring data structure definitions;

    - Networking subsytem;

    - Amateur Radio drivers;

    - XFRM subsystem;

    - Tracing infrastructure;

    - BPF subsystem;

    - Kernel CPU control infrastructure;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Memory management;

    - Bluetooth subsystem;

    - DCCP (Datagram Congestion Control Protocol);

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - RxRPC session sockets;

    - Network traffic control;

    - VMware vSockets driver;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module;

    - SoC audio core drivers; (CVE-2025-21830, CVE-2025-21678, CVE-2025-21815, CVE-2024-57974, CVE-2025-21725,     CVE-2025-21718, CVE-2025-21748, CVE-2025-21732, CVE-2024-57953, CVE-2025-21727, CVE-2025-21816,     CVE-2025-21719, CVE-2024-53124, CVE-2024-58019, CVE-2025-38001, CVE-2025-21720, CVE-2025-21734,     CVE-2025-21672, CVE-2025-21692, CVE-2024-58076, CVE-2025-21694, CVE-2024-58061, CVE-2025-21714,     CVE-2025-21689, CVE-2024-49887, CVE-2024-57949, CVE-2025-38177, CVE-2025-21683, CVE-2025-21669,     CVE-2025-21722, CVE-2024-57980, CVE-2025-38000, CVE-2025-37932, CVE-2024-58034, CVE-2024-58081,     CVE-2025-21733, CVE-2025-21682, CVE-2024-57924, CVE-2025-21743, CVE-2024-57975, CVE-2025-37798,     CVE-2024-58058, CVE-2025-21809, CVE-2025-21676, CVE-2024-57993, CVE-2025-21699, CVE-2024-58016,     CVE-2025-21832, CVE-2025-21804, CVE-2024-58011, CVE-2024-58007, CVE-2025-21826, CVE-2024-58055,     CVE-2025-21668, CVE-2025-21715, CVE-2024-58078, CVE-2025-21829, CVE-2025-21811, CVE-2025-21814,     CVE-2024-58053, CVE-2025-21726, CVE-2025-21943, CVE-2025-37750, CVE-2025-21673, CVE-2024-57984,     CVE-2025-37997, CVE-2025-21684, CVE-2025-21750, CVE-2024-58013, CVE-2025-21799, CVE-2024-58083,     CVE-2025-21798, CVE-2025-21731, CVE-2025-21708, CVE-2024-57986, CVE-2025-21744, CVE-2024-58014,     CVE-2025-21721, CVE-2024-58063, CVE-2024-57979, CVE-2024-58005, CVE-2025-21728, CVE-2025-21681,     CVE-2025-21806, CVE-2024-57982, CVE-2024-58002, CVE-2024-58082, CVE-2025-21812, CVE-2025-21745,     CVE-2024-58017, CVE-2025-21665, CVE-2025-21828, CVE-2025-37890, CVE-2024-57952, CVE-2024-57997,     CVE-2025-21825, CVE-2025-21716, CVE-2024-57948, CVE-2025-21710, CVE-2025-21674, CVE-2025-21675,     CVE-2024-50157, CVE-2025-21738, CVE-2025-22088, CVE-2024-58071, CVE-2024-58085, CVE-2025-21723,     CVE-2025-21690, CVE-2025-21670, CVE-2025-21741, CVE-2024-57999, CVE-2025-21691, CVE-2024-58068,     CVE-2024-58057, CVE-2024-57994, CVE-2024-58072, CVE-2025-21742, CVE-2024-58006, CVE-2024-58077,     CVE-2024-58003, CVE-2025-21753, CVE-2024-57981, CVE-2024-57973, CVE-2024-58001, CVE-2025-21666,     CVE-2025-21810, CVE-2025-21808, CVE-2024-57996, CVE-2024-58054, CVE-2024-57998, CVE-2025-21707,     CVE-2025-21736, CVE-2025-21820, CVE-2025-21739, CVE-2024-57951, CVE-2025-21667, CVE-2024-58070,     CVE-2025-21801, CVE-2024-58051, CVE-2024-58079, CVE-2025-21754, CVE-2024-58069, CVE-2025-37974,     CVE-2025-21802, CVE-2025-21749, CVE-2024-57990, CVE-2024-58080, CVE-2025-21705, CVE-2025-21697,     CVE-2024-58052, CVE-2025-21711, CVE-2024-58056, CVE-2025-21724, CVE-2024-58018, CVE-2025-21735,     CVE-2024-58010, CVE-2025-21680)

Tenable has extracted the preceding description block directly from the Ubuntu 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 Ubuntu 22.04 LTS / 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7595-1 advisory.

    It was discovered that the CIFS network file system implementation in the Linux kernel did not properly     verify the target namespace when handling upcalls. An attacker could use this to expose sensitive     information. (CVE-2025-2312)

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - GPIO subsystem;

    - GPU drivers;

    - InfiniBand drivers;

    - IRQ chip drivers;

    - Network drivers;

    - Mellanox network drivers;

    - i.MX PM domains;

    - SCSI subsystem;

    - USB Serial drivers;

    - AFS file system;

    - GFS2 file system;

    - File systems infrastructure;

    - File system notification infrastructure;

    - Overlay file system;

    - Proc file system;

    - SMB network file system;

    - Timer subsystem;

    - Kernel CPU control infrastructure;

    - Memory management;

    - Networking core;

    - DCCP (Datagram Congestion Control Protocol);

    - IPv6 networking;

    - IEEE 802.15.4 subsystem;

    - Open vSwitch;

    - Network traffic control;

    - VMware vSockets driver; (CVE-2025-21943, CVE-2025-21672, CVE-2024-57952, CVE-2024-57949, CVE-2025-21683,     CVE-2025-21690, CVE-2025-21699, CVE-2025-21676, CVE-2024-57924, CVE-2025-21694, CVE-2024-57948,     CVE-2025-21675, CVE-2024-57951, CVE-2025-21692, CVE-2025-21684, CVE-2025-21668, CVE-2025-21665,     CVE-2025-21667, CVE-2025-21670, CVE-2025-21674, CVE-2025-21697, CVE-2024-53124, CVE-2025-21666,     CVE-2025-21682, CVE-2025-21680, CVE-2025-21681, CVE-2025-21691, CVE-2025-21669, CVE-2025-21673,     CVE-2024-50157, CVE-2025-21689, CVE-2025-21678)

Tenable has extracted the preceding description block directly from the Ubuntu 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 Ubuntu 22.04 LTS / 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7596-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - GPIO subsystem;

    - GPU drivers;

    - InfiniBand drivers;

    - IRQ chip drivers;

    - Network drivers;

    - Mellanox network drivers;

    - i.MX PM domains;

    - SCSI subsystem;

    - USB Serial drivers;

    - AFS file system;

    - GFS2 file system;

    - File systems infrastructure;

    - File system notification infrastructure;

    - Overlay file system;

    - Proc file system;

    - SMB network file system;

    - Timer subsystem;

    - Kernel CPU control infrastructure;

    - Memory management;

    - Networking core;

    - DCCP (Datagram Congestion Control Protocol);

    - IPv6 networking;

    - IEEE 802.15.4 subsystem;

    - Open vSwitch;

    - Network traffic control;

    - VMware vSockets driver; (CVE-2025-21675, CVE-2025-21697, CVE-2025-21668, CVE-2024-57951, CVE-2025-21680,     CVE-2024-50157, CVE-2025-21699, CVE-2025-21669, CVE-2025-21678, CVE-2025-21665, CVE-2024-57924,     CVE-2024-57949, CVE-2024-53124, CVE-2025-21684, CVE-2025-21676, CVE-2025-21672, CVE-2025-21682,     CVE-2025-21670, CVE-2025-21690, CVE-2025-21673, CVE-2025-21691, CVE-2024-57952, CVE-2025-21674,     CVE-2025-21689, CVE-2025-21943, CVE-2025-21692, CVE-2025-21667, CVE-2025-21666, CVE-2024-57948,     CVE-2025-21694, CVE-2025-21683, CVE-2025-21681)

Tenable has extracted the preceding description block directly from the Ubuntu 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 Ubuntu 24.04 LTS / 24.10 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7448-1 advisory.

    It was discovered that the CIFS network file system implementation in the Linux kernel did not properly     verify the target namespace when handling upcalls. An attacker could use this to expose sensitive     information. (CVE-2025-2312)

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - GPIO subsystem;

    - GPU drivers;

    - IRQ chip drivers;

    - Network drivers;

    - Mellanox network drivers;

    - x86 platform drivers;

    - i.MX PM domains;

    - SCSI subsystem;

    - USB Serial drivers;

    - AFS file system;

    - GFS2 file system;

    - File systems infrastructure;

    - Proc file system;

    - SMB network file system;

    - Timer subsystem;

    - Kernel CPU control infrastructure;

    - Memory management;

    - Networking core;

    - Ethtool driver;

    - IEEE 802.15.4 subsystem;

    - Open vSwitch;

    - Network traffic control;

    - VMware vSockets driver; (CVE-2025-21694, CVE-2025-21993, CVE-2025-21684, CVE-2025-21681, CVE-2025-21675,     CVE-2025-21672, CVE-2025-21696, CVE-2025-21691, CVE-2025-21683, CVE-2025-21666, CVE-2025-21682,     CVE-2025-21697, CVE-2025-21668, CVE-2025-21701, CVE-2025-21670, CVE-2025-21676, CVE-2025-21695,     CVE-2025-21692, CVE-2025-21674, CVE-2025-21699, CVE-2024-57948, CVE-2025-21677, CVE-2024-57951,     CVE-2025-21702, CVE-2025-21700, CVE-2024-57949, CVE-2025-21669, CVE-2025-21703, CVE-2025-21756,     CVE-2025-21667, CVE-2024-57952, CVE-2024-57950, CVE-2025-21685, CVE-2025-21693, CVE-2025-21678,     CVE-2025-21665, CVE-2025-21680, CVE-2025-21689, CVE-2025-21690, CVE-2025-21673)

Tenable has extracted the preceding description block directly from the Ubuntu 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 Ubuntu 24.04 LTS / 24.10 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7445-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - GPIO subsystem;

    - GPU drivers;

    - IRQ chip drivers;

    - Network drivers;

    - Mellanox network drivers;

    - x86 platform drivers;

    - i.MX PM domains;

    - SCSI subsystem;

    - USB Serial drivers;

    - AFS file system;

    - GFS2 file system;

    - File systems infrastructure;

    - Proc file system;

    - SMB network file system;

    - Timer subsystem;

    - Kernel CPU control infrastructure;

    - Memory management;

    - Networking core;

    - Ethtool driver;

    - IEEE 802.15.4 subsystem;

    - Open vSwitch;

    - Network traffic control;

    - VMware vSockets driver; (CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670, CVE-2024-57949,     CVE-2025-21677, CVE-2025-21680, CVE-2025-21703, CVE-2024-57952, CVE-2025-21674, CVE-2025-21701,     CVE-2025-21691, CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683, CVE-2025-21675,     CVE-2025-21672, CVE-2024-57948, CVE-2025-21669, CVE-2025-21673, CVE-2025-21692, CVE-2025-21699,     CVE-2025-21702, CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695, CVE-2025-21696,     CVE-2025-21700, CVE-2025-21678, CVE-2025-21676, CVE-2024-57950, CVE-2025-21666, CVE-2025-21694,     CVE-2025-21693, CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)

Tenable has extracted the preceding description block directly from the Ubuntu 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.

  - In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Don't enable     interrupts in its_irq_set_vcpu_affinity() The following call-chain leads to enabling interrupts in a     nested interrupt disabled section: irq_set_vcpu_affinity() irq_get_desc_lock() raw_spin_lock_irqsave()     <--- Disable interrupts its_irq_set_vcpu_affinity() guard(raw_spinlock_irq) <--- Enables interrupts when     leaving the guard() irq_put_desc_unlock() <--- Warns because interrupts are enabled This was broken in     commit b97e8a2f7130, which replaced the original raw_spin_[un]lock() pair with guard(raw_spinlock_irq).
    Fix the issue by using guard(raw_spinlock). [ tglx: Massaged change log ] (CVE-2024-57949)

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

The remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-4076 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4076-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     March 01, 2025                                https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.6.1.128-1~deb11u1     CVE ID         : CVE-2022-49034 CVE-2023-52916 CVE-2023-52926 CVE-2024-26595                      CVE-2024-27407 CVE-2024-35870 CVE-2024-35956 CVE-2024-36476                      CVE-2024-36479 CVE-2024-36899 CVE-2024-37021 CVE-2024-39282                      CVE-2024-41014 CVE-2024-42252 CVE-2024-42315 CVE-2024-42319                      CVE-2024-43098 CVE-2024-44950 CVE-2024-45828 CVE-2024-46809                      CVE-2024-46841 CVE-2024-46896 CVE-2024-47143 CVE-2024-47408                      CVE-2024-47745 CVE-2024-48881 CVE-2024-49571 CVE-2024-49861                      CVE-2024-49891 CVE-2024-49897 CVE-2024-49898 CVE-2024-49899                      CVE-2024-49909 CVE-2024-49911 CVE-2024-49915 CVE-2024-49917                      CVE-2024-49925 CVE-2024-49929 CVE-2024-49934 CVE-2024-49939                      CVE-2024-49951 CVE-2024-49994 CVE-2024-49996 CVE-2024-50014                      CVE-2024-50047 CVE-2024-50051 CVE-2024-50055 CVE-2024-50121                      CVE-2024-50146 CVE-2024-50164 CVE-2024-50248 CVE-2024-50258                      CVE-2024-50275 CVE-2024-50304 CVE-2024-52332 CVE-2024-53099                      CVE-2024-53105 CVE-2024-53124 CVE-2024-53125 CVE-2024-53128                      CVE-2024-53141 CVE-2024-53142 CVE-2024-53145 CVE-2024-53146                      CVE-2024-53148 CVE-2024-53150 CVE-2024-53151 CVE-2024-53154                      CVE-2024-53155 CVE-2024-53156 CVE-2024-53157 CVE-2024-53158                      CVE-2024-53161 CVE-2024-53164 CVE-2024-53165 CVE-2024-53170                      CVE-2024-53171 CVE-2024-53172 CVE-2024-53173 CVE-2024-53174                      CVE-2024-53175 CVE-2024-53180 CVE-2024-53181 CVE-2024-53183                      CVE-2024-53184 CVE-2024-53190 CVE-2024-53194 CVE-2024-53196                      CVE-2024-53197 CVE-2024-53198 CVE-2024-53206 CVE-2024-53207                      CVE-2024-53208 CVE-2024-53210 CVE-2024-53213 CVE-2024-53214                      CVE-2024-53215 CVE-2024-53217 CVE-2024-53220 CVE-2024-53226                      CVE-2024-53227 CVE-2024-53229 CVE-2024-53230 CVE-2024-53231                      CVE-2024-53233 CVE-2024-53234 CVE-2024-53237 CVE-2024-53239                      CVE-2024-53240 CVE-2024-53241 CVE-2024-53680 CVE-2024-53685                      CVE-2024-53690 CVE-2024-54031 CVE-2024-55881 CVE-2024-55916                      CVE-2024-56369 CVE-2024-56531 CVE-2024-56532 CVE-2024-56533                      CVE-2024-56539 CVE-2024-56546 CVE-2024-56548 CVE-2024-56551                      CVE-2024-56557 CVE-2024-56558 CVE-2024-56562 CVE-2024-56567                      CVE-2024-56568 CVE-2024-56569 CVE-2024-56570 CVE-2024-56572                      CVE-2024-56574 CVE-2024-56575 CVE-2024-56576 CVE-2024-56578                      CVE-2024-56579 CVE-2024-56581 CVE-2024-56582 CVE-2024-56584                      CVE-2024-56585 CVE-2024-56586 CVE-2024-56587 CVE-2024-56589                      CVE-2024-56590 CVE-2024-56593 CVE-2024-56594 CVE-2024-56595                      CVE-2024-56596 CVE-2024-56597 CVE-2024-56598 CVE-2024-56599                      CVE-2024-56600 CVE-2024-56601 CVE-2024-56602 CVE-2024-56603                      CVE-2024-56604 CVE-2024-56605 CVE-2024-56606 CVE-2024-56608                      CVE-2024-56610 CVE-2024-56614 CVE-2024-56615 CVE-2024-56616                      CVE-2024-56619 CVE-2024-56622 CVE-2024-56623 CVE-2024-56625                      CVE-2024-56626 CVE-2024-56627 CVE-2024-56628 CVE-2024-56629                      CVE-2024-56630 CVE-2024-56631 CVE-2024-56633 CVE-2024-56634                      CVE-2024-56636 CVE-2024-56637 CVE-2024-56640 CVE-2024-56642                      CVE-2024-56643 CVE-2024-56644 CVE-2024-56645 CVE-2024-56648                      CVE-2024-56650 CVE-2024-56651 CVE-2024-56658 CVE-2024-56659                      CVE-2024-56660 CVE-2024-56661 CVE-2024-56662 CVE-2024-56663                      CVE-2024-56664 CVE-2024-56665 CVE-2024-56670 CVE-2024-56672                      CVE-2024-56675 CVE-2024-56677 CVE-2024-56678 CVE-2024-56679                      CVE-2024-56681 CVE-2024-56683 CVE-2024-56687 CVE-2024-56688                      CVE-2024-56690 CVE-2024-56691 CVE-2024-56693 CVE-2024-56694                      CVE-2024-56698 CVE-2024-56700 CVE-2024-56701 CVE-2024-56703                      CVE-2024-56704 CVE-2024-56705 CVE-2024-56707 CVE-2024-56708                      CVE-2024-56709 CVE-2024-56715 CVE-2024-56716 CVE-2024-56717                      CVE-2024-56718 CVE-2024-56720 CVE-2024-56722 CVE-2024-56723                      CVE-2024-56724 CVE-2024-56725 CVE-2024-56726 CVE-2024-56727                      CVE-2024-56728 CVE-2024-56739 CVE-2024-56741 CVE-2024-56745                      CVE-2024-56746 CVE-2024-56747 CVE-2024-56748 CVE-2024-56751                      CVE-2024-56754 CVE-2024-56755 CVE-2024-56756 CVE-2024-56759                      CVE-2024-56763 CVE-2024-56765 CVE-2024-56766 CVE-2024-56767                      CVE-2024-56769 CVE-2024-56770 CVE-2024-56774 CVE-2024-56776                      CVE-2024-56777 CVE-2024-56778 CVE-2024-56779 CVE-2024-56780                      CVE-2024-56781 CVE-2024-56783 CVE-2024-56785 CVE-2024-56787                      CVE-2024-57791 CVE-2024-57792 CVE-2024-57798 CVE-2024-57802                      CVE-2024-57807 CVE-2024-57838 CVE-2024-57841 CVE-2024-57849                      CVE-2024-57850 CVE-2024-57874 CVE-2024-57876 CVE-2024-57882                      CVE-2024-57884 CVE-2024-57887 CVE-2024-57889 CVE-2024-57890                      CVE-2024-57892 CVE-2024-57893 CVE-2024-57894 CVE-2024-57896                      CVE-2024-57897 CVE-2024-57900 CVE-2024-57901 CVE-2024-57902                      CVE-2024-57903 CVE-2024-57904 CVE-2024-57906 CVE-2024-57907                      CVE-2024-57908 CVE-2024-57910 CVE-2024-57911 CVE-2024-57912                      CVE-2024-57913 CVE-2024-57916 CVE-2024-57917 CVE-2024-57922                      CVE-2024-57925 CVE-2024-57929 CVE-2024-57930 CVE-2024-57931                      CVE-2024-57938 CVE-2024-57939 CVE-2024-57940 CVE-2024-57946                      CVE-2024-57948 CVE-2024-57949 CVE-2024-57951 CVE-2025-21629                      CVE-2025-21631 CVE-2025-21636 CVE-2025-21637 CVE-2025-21638                      CVE-2025-21639 CVE-2025-21640 CVE-2025-21646 CVE-2025-21647                      CVE-2025-21648 CVE-2025-21653 CVE-2025-21655 CVE-2025-21660                      CVE-2025-21662 CVE-2025-21664 CVE-2025-21665 CVE-2025-21666                      CVE-2025-21667 CVE-2025-21668 CVE-2025-21669 CVE-2025-21671                      CVE-2025-21675 CVE-2025-21678 CVE-2025-21680 CVE-2025-21681                      CVE-2025-21683 CVE-2025-21687 CVE-2025-21688 CVE-2025-21689                      CVE-2025-21690 CVE-2025-21692 CVE-2025-21694 CVE-2025-21697                      CVE-2025-21699

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For Debian 11 bullseye, these problems have been fixed in version     6.1.6.1.128-1~deb11u1.  This additionally includes many more bug fixes     from stable updates 6.1.120-6.1.128 inclusive.

    We recommend that you upgrade your linux-6.1 packages.

    For the detailed security status of linux-6.1 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/linux-6.1

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

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

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2025-823 advisory.

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

    gpiolib: cdev: Fix use after free in lineinfo_changed_notify (CVE-2024-36899)

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

    bpf: Fix overloading of MEM_UNINIT's meaning (CVE-2024-50164)

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

    fs/ntfs3: Add rough attr alloc_size check (CVE-2024-50246)

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

    net: fix data-races around sk->sk_forward_alloc (CVE-2024-53124)

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

    sched/task_stack: fix object_is_on_stack() for KASAN tagged pointers (CVE-2024-53128)

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

    block: fix uaf for flush rq while iterating tags (CVE-2024-53170)

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

    ceph: give up on paths longer than PATH_MAX (CVE-2024-53685)

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

    scsi: sg: Fix slab-use-after-free read in sg_release() (CVE-2024-56631)

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

    bpf, sockmap: Fix race between element replace and close() (CVE-2024-56664)

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

    topology: Keep the cpumask unchanged when printing cpumap (CVE-2024-57917)

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

    dm array: fix releasing a faulty array block twice in dm_array_cursor_end (CVE-2024-57929)

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

    exfat: fix the infinite loop in exfat_readdir() (CVE-2024-57940)

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

    irqchip/gic-v3-its: Don't enable interrupts in its_irq_set_vcpu_affinity() (CVE-2024-57949)

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

    hrtimers: Handle CPU state correctly on hotplug (CVE-2024-57951)

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

    block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)

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

    sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy (CVE-2025-21636)

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

    sctp: sysctl: udp_port: avoid using current->nsproxy (CVE-2025-21637)

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

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

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

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

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

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

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

    sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)

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

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

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

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

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

    io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (CVE-2025-21655)

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

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

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

    dm thin: make get_first_thin use rcu-safe list first function (CVE-2025-21664)

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

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

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

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

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

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

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

    zram: fix potential UAF of zram table (CVE-2025-21671)

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

    net/mlx5: Clear port select structure when fail to create (CVE-2025-21675)

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

    gtp: Destroy device along with udp socket's netns dismantle. (CVE-2025-21678)

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

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

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

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

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

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

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
242830	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)	Nessus	NewStart CGSL Local Security Checks	high
242344	Ubuntu 22.04 LTS : Linux kernel (HWE) vulnerabilities (USN-7653-1)	Nessus	Ubuntu Local Security Checks	high
240566	Ubuntu 22.04 LTS / 24.04 LTS : Linux kernel vulnerabilities (USN-7595-1)	Nessus	Ubuntu Local Security Checks	high
240564	Ubuntu 22.04 LTS / 24.04 LTS : Linux kernel (Azure) vulnerabilities (USN-7596-1)	Nessus	Ubuntu Local Security Checks	high
234778	Ubuntu 24.04 LTS / 24.10 : Linux kernel vulnerabilities (USN-7448-1)	Nessus	Ubuntu Local Security Checks	high
234757	Ubuntu 24.04 LTS / 24.10 : Linux kernel vulnerabilities (USN-7445-1)	Nessus	Ubuntu Local Security Checks	high
231876	Linux Distros Unpatched Vulnerability : CVE-2024-57949	Nessus	Misc.	medium
216985	Debian dla-4076 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	high
215034	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2025-823)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2024-57949

medium

Tenable Plugins

high

high

high

high

high

high

medium

high

high