In the Linux kernel, the following vulnerability has been resolved: i2c: core: fix adapter registration race Adapters can be looked up based on their id using i2c_get_adapter() which takes a reference to the embedded struct device. Make sure that the adapter (including its struct device) has been initialised before adding it to the IDR to avoid accessing uninitialised data which could, for example, lead to NULL-pointer dereferences or use-after-free. Note that the i2c-dev chardev, which is registered from a bus notifier, currently uses i2c_get_adapter() so the adapter needs to be added to the IDR before registration.

An update of the linux package has been released.

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

    - -------------------------------------------------------------------------     Debian LTS Advisory DLA-4723-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/               Emilio Pozuelo Monfort     August 07, 2026                               https://wiki.debian.org/LTS
    - -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.180-1~deb11u1     CVE ID         : CVE-2024-36013 CVE-2025-40196 CVE-2026-31610 CVE-2026-43216                      CVE-2026-46135 CVE-2026-53332 CVE-2026-53392 CVE-2026-53393                      CVE-2026-53399 CVE-2026-53400 CVE-2026-53402 CVE-2026-63797                      CVE-2026-63806 CVE-2026-63810 CVE-2026-63815 CVE-2026-63818                      CVE-2026-63829 CVE-2026-64187 CVE-2026-64189 CVE-2026-64206                      CVE-2026-64248 CVE-2026-64250 CVE-2026-64266 CVE-2026-64268                      CVE-2026-64269 CVE-2026-64271 CVE-2026-64273 CVE-2026-64274                      CVE-2026-64275 CVE-2026-64276 CVE-2026-64277 CVE-2026-64279                      CVE-2026-64296 CVE-2026-64297 CVE-2026-64298 CVE-2026-64299                      CVE-2026-64301 CVE-2026-64303 CVE-2026-64304 CVE-2026-64306                      CVE-2026-64312 CVE-2026-64313 CVE-2026-64315 CVE-2026-64316                      CVE-2026-64317 CVE-2026-64318 CVE-2026-64322 CVE-2026-64323                      CVE-2026-64324 CVE-2026-64329 CVE-2026-64330 CVE-2026-64331                      CVE-2026-64332 CVE-2026-64333 CVE-2026-64334 CVE-2026-64335                      CVE-2026-64336 CVE-2026-64337 CVE-2026-64338 CVE-2026-64340                      CVE-2026-64342 CVE-2026-64343 CVE-2026-64344 CVE-2026-64346                      CVE-2026-64347 CVE-2026-64350 CVE-2026-64351 CVE-2026-64352                      CVE-2026-64355 CVE-2026-64359 CVE-2026-64360 CVE-2026-64361                      CVE-2026-64362 CVE-2026-64363 CVE-2026-64364 CVE-2026-64365                      CVE-2026-64370 CVE-2026-64371 CVE-2026-64372 CVE-2026-64373                      CVE-2026-64374 CVE-2026-64375 CVE-2026-64376 CVE-2026-64378                      CVE-2026-64379 CVE-2026-64380 CVE-2026-64381 CVE-2026-64390                      CVE-2026-64393 CVE-2026-64394 CVE-2026-64395 CVE-2026-64396                      CVE-2026-64397 CVE-2026-64398 CVE-2026-64399 CVE-2026-64401                      CVE-2026-64403 CVE-2026-64406 CVE-2026-64408 CVE-2026-64409                      CVE-2026-64411 CVE-2026-64412 CVE-2026-64413 CVE-2026-64417                      CVE-2026-64419 CVE-2026-64420 CVE-2026-64422 CVE-2026-64423                      CVE-2026-64425 CVE-2026-64428 CVE-2026-64429 CVE-2026-64430                      CVE-2026-64432 CVE-2026-64435 CVE-2026-64436 CVE-2026-64437                      CVE-2026-64438 CVE-2026-64440 CVE-2026-64441 CVE-2026-64442                      CVE-2026-64443 CVE-2026-64444 CVE-2026-64445 CVE-2026-64446                      CVE-2026-64448 CVE-2026-64449 CVE-2026-64450 CVE-2026-64452                      CVE-2026-64454 CVE-2026-64455 CVE-2026-64456 CVE-2026-64458                      CVE-2026-64461 CVE-2026-64462 CVE-2026-64465 CVE-2026-64468                      CVE-2026-64469 CVE-2026-64470 CVE-2026-64471 CVE-2026-64472                      CVE-2026-64475 CVE-2026-64476 CVE-2026-64478 CVE-2026-64480                      CVE-2026-64482 CVE-2026-64483 CVE-2026-64484 CVE-2026-64486                      CVE-2026-64487 CVE-2026-64488 CVE-2026-64489 CVE-2026-64494                      CVE-2026-64495 CVE-2026-64496 CVE-2026-64497 CVE-2026-64500                      CVE-2026-64503 CVE-2026-64504 CVE-2026-64505 CVE-2026-64510                      CVE-2026-64512 CVE-2026-64514 CVE-2026-64530 CVE-2026-64531                      CVE-2026-64532 CVE-2026-64533 CVE-2026-64534 CVE-2026-64535                      CVE-2026-64536 CVE-2026-64537 CVE-2026-64538 CVE-2026-64539                      CVE-2026-64540 CVE-2026-64541 CVE-2026-64544 CVE-2026-64545                      CVE-2026-64546 CVE-2026-64547 CVE-2026-64548 CVE-2026-64549                      CVE-2026-64550 CVE-2026-64551 CVE-2026-64552 CVE-2026-64553                      CVE-2026-64554 CVE-2026-64557 CVE-2026-64560 CVE-2026-64600

    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.180-1~deb11u1. This version additionally includes many more bug fixes     from stable update 6.1.178-6.1.180.

    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

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.

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

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4720-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     August 05, 2026                               https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux     Version        : 6.1.180-1     CVE ID         : CVE-2024-36013 CVE-2025-40196 CVE-2026-31610 CVE-2026-43216                      CVE-2026-46135 CVE-2026-53332 CVE-2026-53392 CVE-2026-53393                      CVE-2026-53399 CVE-2026-53400 CVE-2026-53402 CVE-2026-63797                      CVE-2026-63806 CVE-2026-63810 CVE-2026-63815 CVE-2026-63818                      CVE-2026-63829 CVE-2026-64187 CVE-2026-64189 CVE-2026-64206                      CVE-2026-64248 CVE-2026-64250 CVE-2026-64266 CVE-2026-64268                      CVE-2026-64269 CVE-2026-64271 CVE-2026-64273 CVE-2026-64274                      CVE-2026-64275 CVE-2026-64276 CVE-2026-64277 CVE-2026-64279                      CVE-2026-64296 CVE-2026-64297 CVE-2026-64298 CVE-2026-64299                      CVE-2026-64301 CVE-2026-64303 CVE-2026-64304 CVE-2026-64306                      CVE-2026-64312 CVE-2026-64313 CVE-2026-64315 CVE-2026-64316                      CVE-2026-64317 CVE-2026-64318 CVE-2026-64322 CVE-2026-64323                      CVE-2026-64324 CVE-2026-64329 CVE-2026-64330 CVE-2026-64331                      CVE-2026-64332 CVE-2026-64333 CVE-2026-64334 CVE-2026-64335                      CVE-2026-64336 CVE-2026-64337 CVE-2026-64338 CVE-2026-64340                      CVE-2026-64342 CVE-2026-64343 CVE-2026-64344 CVE-2026-64346                      CVE-2026-64347 CVE-2026-64350 CVE-2026-64351 CVE-2026-64352                      CVE-2026-64355 CVE-2026-64359 CVE-2026-64360 CVE-2026-64361                      CVE-2026-64362 CVE-2026-64363 CVE-2026-64364 CVE-2026-64365                      CVE-2026-64370 CVE-2026-64371 CVE-2026-64372 CVE-2026-64373                      CVE-2026-64374 CVE-2026-64375 CVE-2026-64376 CVE-2026-64378                      CVE-2026-64379 CVE-2026-64380 CVE-2026-64381 CVE-2026-64390                      CVE-2026-64393 CVE-2026-64394 CVE-2026-64395 CVE-2026-64396                      CVE-2026-64397 CVE-2026-64398 CVE-2026-64399 CVE-2026-64401                      CVE-2026-64403 CVE-2026-64406 CVE-2026-64408 CVE-2026-64409                      CVE-2026-64411 CVE-2026-64412 CVE-2026-64413 CVE-2026-64417                      CVE-2026-64419 CVE-2026-64420 CVE-2026-64422 CVE-2026-64423                      CVE-2026-64425 CVE-2026-64428 CVE-2026-64429 CVE-2026-64430                      CVE-2026-64432 CVE-2026-64435 CVE-2026-64436 CVE-2026-64437                      CVE-2026-64438 CVE-2026-64440 CVE-2026-64441 CVE-2026-64442                      CVE-2026-64443 CVE-2026-64444 CVE-2026-64445 CVE-2026-64446                      CVE-2026-64448 CVE-2026-64449 CVE-2026-64450 CVE-2026-64452                      CVE-2026-64454 CVE-2026-64455 CVE-2026-64456 CVE-2026-64458                      CVE-2026-64461 CVE-2026-64462 CVE-2026-64465 CVE-2026-64468                      CVE-2026-64469 CVE-2026-64470 CVE-2026-64471 CVE-2026-64472                      CVE-2026-64475 CVE-2026-64476 CVE-2026-64478 CVE-2026-64480                      CVE-2026-64482 CVE-2026-64483 CVE-2026-64484 CVE-2026-64486                      CVE-2026-64487 CVE-2026-64488 CVE-2026-64489 CVE-2026-64494                      CVE-2026-64495 CVE-2026-64496 CVE-2026-64497 CVE-2026-64500                      CVE-2026-64503 CVE-2026-64504 CVE-2026-64505 CVE-2026-64510                      CVE-2026-64512 CVE-2026-64514 CVE-2026-64530 CVE-2026-64531                      CVE-2026-64532 CVE-2026-64533 CVE-2026-64534 CVE-2026-64535                      CVE-2026-64536 CVE-2026-64537 CVE-2026-64538 CVE-2026-64539                      CVE-2026-64540 CVE-2026-64541 CVE-2026-64544 CVE-2026-64545                      CVE-2026-64546 CVE-2026-64547 CVE-2026-64548 CVE-2026-64549                      CVE-2026-64550 CVE-2026-64551 CVE-2026-64552 CVE-2026-64553                      CVE-2026-64554 CVE-2026-64557 CVE-2026-64560 CVE-2026-64600

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

    For Debian 12 bookworm, these problems have been fixed in version     6.1.180-1.  This version additionally includes many more bug fixes     from stable update 6.1.178-6.1.180.

    We recommend that you upgrade your linux packages.

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

    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.

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

    - -------------------------------------------------------------------------     Debian LTS Advisory DLA-4717-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/               Emilio Pozuelo Monfort     August 05, 2026                               https://wiki.debian.org/LTS
    - -------------------------------------------------------------------------

    Package        : linux     Version        : 5.10.262-1     CVE ID         : CVE-2022-49803 CVE-2022-50114 CVE-2023-52494 CVE-2025-23131                      CVE-2025-39931 CVE-2026-23204 CVE-2026-31451 CVE-2026-31755                      CVE-2026-43216 CVE-2026-43219 CVE-2026-43499 CVE-2026-46116                      CVE-2026-46135 CVE-2026-46252 CVE-2026-46331 CVE-2026-52942                      CVE-2026-53138 CVE-2026-53157 CVE-2026-53158 CVE-2026-53159                      CVE-2026-53167 CVE-2026-53177 CVE-2026-53325 CVE-2026-53329                      CVE-2026-53332 CVE-2026-53381 CVE-2026-53382 CVE-2026-53385                      CVE-2026-53392 CVE-2026-53393 CVE-2026-53397 CVE-2026-53398                      CVE-2026-53399 CVE-2026-53400 CVE-2026-53402 CVE-2026-53403                      CVE-2026-63794 CVE-2026-63796 CVE-2026-63798 CVE-2026-63800                      CVE-2026-63801 CVE-2026-63803 CVE-2026-63806 CVE-2026-63808                      CVE-2026-63809 CVE-2026-63814 CVE-2026-63815 CVE-2026-63818                      CVE-2026-63822 CVE-2026-63823 CVE-2026-63824 CVE-2026-63827                      CVE-2026-63828 CVE-2026-63829 CVE-2026-63830 CVE-2026-63831                      CVE-2026-63834 CVE-2026-63835 CVE-2026-63836 CVE-2026-64188                      CVE-2026-64189 CVE-2026-64191 CVE-2026-64206 CVE-2026-64249                      CVE-2026-64252 CVE-2026-64266 CVE-2026-64268 CVE-2026-64271                      CVE-2026-64273 CVE-2026-64274 CVE-2026-64275 CVE-2026-64276                      CVE-2026-64277 CVE-2026-64296 CVE-2026-64298 CVE-2026-64299                      CVE-2026-64303 CVE-2026-64304 CVE-2026-64306 CVE-2026-64312                      CVE-2026-64313 CVE-2026-64315 CVE-2026-64316 CVE-2026-64317                      CVE-2026-64318 CVE-2026-64322 CVE-2026-64323 CVE-2026-64324                      CVE-2026-64329 CVE-2026-64330 CVE-2026-64331 CVE-2026-64332                      CVE-2026-64333 CVE-2026-64334 CVE-2026-64335 CVE-2026-64337                      CVE-2026-64338 CVE-2026-64340 CVE-2026-64342 CVE-2026-64343                      CVE-2026-64344 CVE-2026-64345 CVE-2026-64347 CVE-2026-64348                      CVE-2026-64351 CVE-2026-64359 CVE-2026-64360 CVE-2026-64361                      CVE-2026-64362 CVE-2026-64363 CVE-2026-64364 CVE-2026-64370                      CVE-2026-64371 CVE-2026-64372 CVE-2026-64373 CVE-2026-64374                      CVE-2026-64375 CVE-2026-64378 CVE-2026-64379 CVE-2026-64380                      CVE-2026-64381 CVE-2026-64403 CVE-2026-64406 CVE-2026-64408                      CVE-2026-64411 CVE-2026-64412 CVE-2026-64413 CVE-2026-64420                      CVE-2026-64422 CVE-2026-64423 CVE-2026-64425 CVE-2026-64429                      CVE-2026-64435 CVE-2026-64436 CVE-2026-64438 CVE-2026-64442                      CVE-2026-64445 CVE-2026-64446 CVE-2026-64448 CVE-2026-64450                      CVE-2026-64452 CVE-2026-64455 CVE-2026-64456 CVE-2026-64461                      CVE-2026-64462 CVE-2026-64465 CVE-2026-64468 CVE-2026-64469                      CVE-2026-64470 CVE-2026-64471 CVE-2026-64475 CVE-2026-64478                      CVE-2026-64483 CVE-2026-64484 CVE-2026-64487 CVE-2026-64488                      CVE-2026-64494 CVE-2026-64495 CVE-2026-64496 CVE-2026-64497                      CVE-2026-64500 CVE-2026-64503 CVE-2026-64504 CVE-2026-64505                      CVE-2026-64510 CVE-2026-64514 CVE-2026-64529 CVE-2026-64534                      CVE-2026-64538 CVE-2026-64540 CVE-2026-64541 CVE-2026-64544                      CVE-2026-64546 CVE-2026-64547 CVE-2026-64548 CVE-2026-64549                      CVE-2026-64550 CVE-2026-64551 CVE-2026-64553 CVE-2026-64554                      CVE-2026-64560

    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     5.10.262-1. This version additionally includes many more bug fixes     from stable updates 5.10.260-5.10.262.

    We recommend that you upgrade your linux packages.

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

    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

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-2026-2014 advisory.

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

    ipv6: use RCU in ip6_output() (CVE-2025-40158)

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

    gpio: Fix resource leaks on errors in gpiochip_add_data_with_key() (CVE-2026-31732)

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

    bpf: Reject sleepable kprobe_multi programs at attach time (CVE-2026-43010)

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

    net: Drop the lock in skb_may_tx_timestamp() (CVE-2026-43216)

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

    bpf: Fix tcx/netkit detach permissions when prog fd isn't given (CVE-2026-45932)

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

    ip6_vti: set netns_immutable on the fallback device. (CVE-2026-52909)

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

    bonding: 3ad: implement proper RCU rules for port->aggregator (CVE-2026-52975)

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

    sched/psi: fix race between file release and pressure write (CVE-2026-52991)

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

    sctp: disable BH before calling udp_tunnel_xmit_skb() (CVE-2026-53070)

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

    fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios (CVE-2026-53167)

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

    fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh() (CVE-2026-53341)

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

    af_unix: Set gc_in_progress to true in unix_gc(). (CVE-2026-53361)

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

    virtiofs: fix UAF on submount umount

    iput() called from fuse_release_end() can Oops if the super block hasalready been destroyed.  Normally     this is prevented by waiting fornum_waiting to go down to zero before commencing with super block     shutdown.

    This only works, however, for the last submount instance, as the waitcounter is per connection, not per     superblock.

    Revert to using synchronous release requests for the auto_submounts case,which is virtiofs only at this     time. (CVE-2026-53381)

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

    vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write

    A KASAN null-ptr-deref was observed in vcs_notifier():

    BUG: KASAN: null-ptr-deref in vcs_notifier+0x98/0x130Read of size 2 at addr qmp_cmd_name:
    qmp_capabilities, arguments: {}

    The issue is a race condition in vcs_write(). When the console_lock istemporarily dropped (to copy data     from userspace), the vc_data pointerobtained from vcs_vc() may become stale. After re-acquiring the     lock,vcs_vc() is called again to re-validate the pointer. If the vc has beendeallocated in the meantime,     vcs_vc() returns NULL, and the while loopbreaks (with written > 0). However, after the loop,     vcs_scr_updated(vc)is still called with the now-NULL vc pointer, leading to a null pointerdereference in     the notifier chain (vcs_notifier dereferences param->vc).

    Fix this by adding a NULL check for vc before calling vcs_scr_updated(). (CVE-2026-53385)

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

    fuse: re-lock request before replacing page cache folio

    fuse_try_move_folio() unlocks the request on entry but does notre-lock it on the success path. This means     fuse_chan_abort() can end therequest and free the fuse_io_args (eg fuse_readpages_end()) while     thesubsequent copy chain logic after fuse_try_move_folio() accesses thefuse_io_args, leading to use-after-     free issues.

    Fix this by calling lock_request() before replace_page_cache_folio().This ensures the request is locked on     the success path which willprevent the fuse_io_args from being freed while the later copying logicruns,     and also ensures that the ap->folios[i]->mapping is never nullsince ap->folios[i] will always point to the     newfolio afterreplace_page_cache_folio(). (CVE-2026-53388)

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

    NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)

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

    nfsd: reset write verifier on deferred writeback errors (CVE-2026-53393)

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

    nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race (CVE-2026-53394)

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

    nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)

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

    NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)

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

    i2c: core: fix adapter registration race

    Adapters can be looked up based on their id using i2c_get_adapter()which takes a reference to the embedded     struct device.

    Make sure that the adapter (including its struct device) has beeninitialised before adding it to the IDR     to avoid accessing uninitialiseddata which could, for example, lead to NULL-pointer dereferences oruse-     after-free.

    Note that the i2c-dev chardev, which is registered from a bus notifier,currently uses i2c_get_adapter() so     the adapter needs to be added to theIDR before registration. (CVE-2026-53400)

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

    fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var

    info->var, a framebuffer's current mode, is expected to have a matchingentry in info->modelist.
    var_to_display() relies on this and treats afailed fb_match_mode() as This should not happen.
    fb_set_var() keeps ittrue by adding the mode to the list on every change, anddo_register_framebuffer()     does the same at registration.

    store_modes() replaces the modelist from userspace. fb_new_modelist()validates the new modes but does not     check that info->var still has amatch. It relies on fbcon_new_modelist() to re-point consoles, but     thatonly handles consoles mapped to the framebuffer. With fbcon unbound thereare none, so info->var is     left describing a mode that is no longer in thelist.

    A later console takeover runs var_to_display(), where fb_match_mode()returns NULL and leaves     fb_display[i].mode NULL. fbcon_switch() passes itto display_to_var(), and fb_videomode_to_var()     dereferences the NULL mode.

    Keep the current mode in the list in fb_new_modelist(), the same wayfb_set_var() does. (CVE-2026-53403)

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

    pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)

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

    tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (CVE-2026-63801)

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

    blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)

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

    KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (CVE-2026-63806)

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

    KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (CVE-2026-63807)

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

    exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)

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

    bpf: use kvfree() for replaced sysctl write buffer (CVE-2026-63809)

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

    block: Avoid mounting the bdev pseudo-filesystem in userspace (CVE-2026-63810)

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

    keys: Pin request_key_auth payload in instantiate paths (CVE-2026-63823)

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

    KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)

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

    fbdev: fix use-after-free in store_modes() (CVE-2026-63826)

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

    net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink (CVE-2026-63829)

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

    net: skmsg: preserve sg.copy across SG transforms (CVE-2026-63830)

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

    ntfs3: reject direct userspace writes to reserved $LX* xattrs

    NTFS3 uses $LXUID, $LXGID, $LXMOD and $LXDEV as internal WSLpermission metadata and reloads them into     i_uid, i_gid and i_modefrom ntfs_get_wsl_perm().

    Because the empty-prefix xattr handler also lets file owners callsetxattr() on these names directly, an     unprivileged writer on awritable ntfs3 mount can plant root ownership and S_ISUID on their ownfile and     gain euid 0 after inode reload.

    Reject direct userspace writes to the reserved $LX* names. Internalntfs3 metadata updates are unchanged     because ntfs_save_wsl_perm()writes them via ntfs_set_ea() directly.

    [almaz.alexandrovich@paragon-software.com: added an additional check for non privileged users]     (CVE-2026-63833)

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

    drivers/base/memory: set mem->altmap after successful device registration (CVE-2026-64244)

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

    fbdev: modedb: fix a possible UAF in fb_find_mode() (CVE-2026-64245)

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

    KVM: x86: hyper-v: Bound the bank index when querying sparse banks (CVE-2026-64247)

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

    MIPS: smp: report dying CPU to RCU in stop_this_cpu() (CVE-2026-64248)

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

    LoongArch: Report dying CPU to RCU in stop_this_cpu() (CVE-2026-64250)

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

    kernel/fork: clear PF_BLOCK_TS in copy_process() (CVE-2026-64253)

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.

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

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

    sctp: disable BH before calling udp_tunnel_xmit_skb() (CVE-2026-53070)

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

    bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops (CVE-2026-53078)

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

    KVM: x86: Fix shadow paging use-after-free due to unexpected role (CVE-2026-53359)

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

    af_unix: Set gc_in_progress to true in unix_gc(). (CVE-2026-53361)

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

    virtiofs: fix UAF on submount umount

    iput() called from fuse_release_end() can Oops if the super block hasalready been destroyed.  Normally     this is prevented by waiting fornum_waiting to go down to zero before commencing with super block     shutdown.

    This only works, however, for the last submount instance, as the waitcounter is per connection, not per     superblock.

    Revert to using synchronous release requests for the auto_submounts case,which is virtiofs only at this     time. (CVE-2026-53381)

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

    vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write

    A KASAN null-ptr-deref was observed in vcs_notifier():

    BUG: KASAN: null-ptr-deref in vcs_notifier+0x98/0x130Read of size 2 at addr qmp_cmd_name:
    qmp_capabilities, arguments: {}

    The issue is a race condition in vcs_write(). When the console_lock istemporarily dropped (to copy data     from userspace), the vc_data pointerobtained from vcs_vc() may become stale. After re-acquiring the     lock,vcs_vc() is called again to re-validate the pointer. If the vc has beendeallocated in the meantime,     vcs_vc() returns NULL, and the while loopbreaks (with written > 0). However, after the loop,     vcs_scr_updated(vc)is still called with the now-NULL vc pointer, leading to a null pointerdereference in     the notifier chain (vcs_notifier dereferences param->vc).

    Fix this by adding a NULL check for vc before calling vcs_scr_updated(). (CVE-2026-53385)

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

    fuse: re-lock request before replacing page cache folio

    fuse_try_move_folio() unlocks the request on entry but does notre-lock it on the success path. This means     fuse_chan_abort() can end therequest and free the fuse_io_args (eg fuse_readpages_end()) while     thesubsequent copy chain logic after fuse_try_move_folio() accesses thefuse_io_args, leading to use-after-     free issues.

    Fix this by calling lock_request() before replace_page_cache_folio().This ensures the request is locked on     the success path which willprevent the fuse_io_args from being freed while the later copying logicruns,     and also ensures that the ap->folios[i]->mapping is never nullsince ap->folios[i] will always point to the     newfolio afterreplace_page_cache_folio(). (CVE-2026-53388)

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

    net/tcp-ao: fix use-after-free of key in del_async path (CVE-2026-53389)

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

    NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)

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

    NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)

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

    nfsd: reset write verifier on deferred writeback errors (CVE-2026-53393)

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

    nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race (CVE-2026-53394)

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

    nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)

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

    NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)

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

    i2c: core: fix adapter registration race

    Adapters can be looked up based on their id using i2c_get_adapter()which takes a reference to the embedded     struct device.

    Make sure that the adapter (including its struct device) has beeninitialised before adding it to the IDR     to avoid accessing uninitialiseddata which could, for example, lead to NULL-pointer dereferences oruse-     after-free.

    Note that the i2c-dev chardev, which is registered from a bus notifier,currently uses i2c_get_adapter() so     the adapter needs to be added to theIDR before registration. (CVE-2026-53400)

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

    fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var

    info->var, a framebuffer's current mode, is expected to have a matchingentry in info->modelist.
    var_to_display() relies on this and treats afailed fb_match_mode() as This should not happen.
    fb_set_var() keeps ittrue by adding the mode to the list on every change, anddo_register_framebuffer()     does the same at registration.

    store_modes() replaces the modelist from userspace. fb_new_modelist()validates the new modes but does not     check that info->var still has amatch. It relies on fbcon_new_modelist() to re-point consoles, but     thatonly handles consoles mapped to the framebuffer. With fbcon unbound thereare none, so info->var is     left describing a mode that is no longer in thelist.

    A later console takeover runs var_to_display(), where fb_match_mode()returns NULL and leaves     fb_display[i].mode NULL. fbcon_switch() passes itto display_to_var(), and fb_videomode_to_var()     dereferences the NULL mode.

    Keep the current mode in the list in fb_new_modelist(), the same wayfb_set_var() does. (CVE-2026-53403)

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

    pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)

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

    tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (CVE-2026-63801)

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

    blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)

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

    KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (CVE-2026-63806)

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

    KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (CVE-2026-63807)

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

    exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)

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

    bpf: use kvfree() for replaced sysctl write buffer (CVE-2026-63809)

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

    block: Avoid mounting the bdev pseudo-filesystem in userspace (CVE-2026-63810)

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

    keys: Pin request_key_auth payload in instantiate paths (CVE-2026-63823)

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

    KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)

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

    fbdev: fix use-after-free in store_modes() (CVE-2026-63826)

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

    apparmor: mediate the implicit connect of TCP fast open sendmsg (CVE-2026-63828)

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

    net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink (CVE-2026-63829)

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

    net: skmsg: preserve sg.copy across SG transforms (CVE-2026-63830)

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

    ntfs3: reject direct userspace writes to reserved $LX* xattrs

    NTFS3 uses $LXUID, $LXGID, $LXMOD and $LXDEV as internal WSLpermission metadata and reloads them into     i_uid, i_gid and i_modefrom ntfs_get_wsl_perm().

    Because the empty-prefix xattr handler also lets file owners callsetxattr() on these names directly, an     unprivileged writer on awritable ntfs3 mount can plant root ownership and S_ISUID on their ownfile and     gain euid 0 after inode reload.

    Reject direct userspace writes to the reserved $LX* names. Internalntfs3 metadata updates are unchanged     because ntfs_save_wsl_perm()writes them via ntfs_set_ea() directly.

    [almaz.alexandrovich@paragon-software.com: added an additional check for non privileged users]     (CVE-2026-63833)

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

    drivers/base/memory: set mem->altmap after successful device registration (CVE-2026-64244)

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

    fbdev: modedb: fix a possible UAF in fb_find_mode() (CVE-2026-64245)

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

    KVM: x86: hyper-v: Bound the bank index when querying sparse banks (CVE-2026-64247)

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

    MIPS: smp: report dying CPU to RCU in stop_this_cpu() (CVE-2026-64248)

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

    LoongArch: Report dying CPU to RCU in stop_this_cpu() (CVE-2026-64250)

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

    kernel/fork: clear PF_BLOCK_TS in copy_process() (CVE-2026-64253)

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

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

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

  - i2c: core: fix adapter registration race Adapters can be looked up based on their id using     i2c_get_adapter() which takes a reference to the embedded struct device. Make sure that the adapter     (including its struct device) has been initialised before adding it to the IDR to avoid accessing     uninitialised data which could, for example, lead to NULL-pointer dereferences or use-after-free. Note     that the i2c-dev chardev, which is registered from a bus notifier, currently uses i2c_get_adapter() so the     adapter needs to be added to the IDR before registration. (CVE-2026-53400)

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

ID	Name	Product	Family	Type	Severity
335080	openSUSE 16: cluster-md-kmp-64kb / cluster-md-kmp-azure / cluster-md-kmp-default / etc (openSUSE-SU-2026:21555-1)	Nessus	SuSE Local Security Checks	Local	high
333954	Photon OS 5.0: Linux PHSA-2026-5.0-92-0916	Nessus	PhotonOS Local Security Checks	Local	high
333520	Debian dla-4723 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	Local	high
332716	Debian dla-4720 : ata-modules-6.1.0-48-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
332715	Debian dla-4717 : ata-modules-5.10.0-43-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
332042	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-2014)	Nessus	Amazon Linux Local Security Checks	Local	medium
328468	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1969)	Nessus	Amazon Linux Local Security Checks	Local	medium
327850	Linux Distros Unpatched Vulnerability : CVE-2026-53400	Nessus	Misc.	Local	high
326038	Photon OS 5.0: Linux PHSA-2026-5.0-0916	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2026-53400

high

Tenable Plugins

high

high

high

high

high

medium

medium

high

high