In the Linux kernel, the following vulnerability has been resolved: net/9p: fix double req put in p9_fd_cancelled Syzkaller reports a KASAN issue as below: general protection fault, probably for non-canonical address 0xfbd59c0000000021: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f] CPU: 0 PID: 5083 Comm: syz-executor.2 Not tainted 6.1.134-syzkaller-00037-g855bd1d7d838 #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 RIP: 0010:__list_del include/linux/list.h:114 [inline] RIP: 0010:__list_del_entry include/linux/list.h:137 [inline] RIP: 0010:list_del include/linux/list.h:148 [inline] RIP: 0010:p9_fd_cancelled+0xe9/0x200 net/9p/trans_fd.c:734 Call Trace: <TASK> p9_client_flush+0x351/0x440 net/9p/client.c:614 p9_client_rpc+0xb6b/0xc70 net/9p/client.c:734 p9_client_version net/9p/client.c:920 [inline] p9_client_create+0xb51/0x1240 net/9p/client.c:1027 v9fs_session_init+0x1f0/0x18f0 fs/9p/v9fs.c:408 v9fs_mount+0xba/0xcb0 fs/9p/vfs_super.c:126 legacy_get_tree+0x108/0x220 fs/fs_context.c:632 vfs_get_tree+0x8e/0x300 fs/super.c:1573 do_new_mount fs/namespace.c:3056 [inline] path_mount+0x6a6/0x1e90 fs/namespace.c:3386 do_mount fs/namespace.c:3399 [inline] __do_sys_mount fs/namespace.c:3607 [inline] __se_sys_mount fs/namespace.c:3584 [inline] __x64_sys_mount+0x283/0x300 fs/namespace.c:3584 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 This happens because of a race condition between: - The 9p client sending an invalid flush request and later cleaning it up; - The 9p client in p9_read_work() canceled all pending requests. Thread 1 Thread 2 ... p9_client_create() ... p9_fd_create() ... p9_conn_create() ... // start Thread 2 INIT_WORK(&m->rq, p9_read_work); p9_read_work() ... p9_client_rpc() ... ... p9_conn_cancel() ... spin_lock(&m->req_lock); ... p9_fd_cancelled() ... ... spin_unlock(&m->req_lock); // status rewrite p9_client_cb(m->client, req, REQ_STATUS_ERROR) // first remove list_del(&req->req_list); ... spin_lock(&m->req_lock) ... // second remove list_del(&req->req_list); spin_unlock(&m->req_lock) ... Commit 74d6a5d56629 ("9p/trans_fd: Fix concurrency del of req_list in p9_fd_cancelled/p9_read_work") fixes a concurrency issue in the 9p filesystem client where the req_list could be deleted simultaneously by both p9_read_work and p9_fd_cancelled functions, but for the case where req->status equals REQ_STATUS_RCVD. Update the check for req->status in p9_fd_cancelled to skip processing not just received requests, but anything that is not SENT, as whatever changed the state from SENT also removed the request from its list. Found by Linux Verification Center (linuxtesting.org) with Syzkaller. [updated the check from status == RECV || status == ERROR to status != SENT]

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

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4379-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     November 25, 2025                             https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.158-1~deb11u1     CVE ID         : CVE-2025-21861 CVE-2025-39929 CVE-2025-39931 CVE-2025-39934                      CVE-2025-39937 CVE-2025-39938 CVE-2025-39942 CVE-2025-39943                      CVE-2025-39944 CVE-2025-39945 CVE-2025-39946 CVE-2025-39949                      CVE-2025-39951 CVE-2025-39953 CVE-2025-39955 CVE-2025-39957                      CVE-2025-39964 CVE-2025-39967 CVE-2025-39968 CVE-2025-39969                      CVE-2025-39970 CVE-2025-39971 CVE-2025-39972 CVE-2025-39973                      CVE-2025-39977 CVE-2025-39978 CVE-2025-39980 CVE-2025-39982                      CVE-2025-39985 CVE-2025-39986 CVE-2025-39987 CVE-2025-39988                      CVE-2025-39993 CVE-2025-39994 CVE-2025-39995 CVE-2025-39996                      CVE-2025-39998 CVE-2025-40001 CVE-2025-40006 CVE-2025-40008                      CVE-2025-40010 CVE-2025-40011 CVE-2025-40013 CVE-2025-40018                      CVE-2025-40019 CVE-2025-40020 CVE-2025-40021 CVE-2025-40022                      CVE-2025-40026 CVE-2025-40027 CVE-2025-40029 CVE-2025-40030                      CVE-2025-40032 CVE-2025-40035 CVE-2025-40036 CVE-2025-40040                      CVE-2025-40042 CVE-2025-40043 CVE-2025-40044 CVE-2025-40048                      CVE-2025-40049 CVE-2025-40051 CVE-2025-40053 CVE-2025-40055                      CVE-2025-40056 CVE-2025-40060 CVE-2025-40062 CVE-2025-40068                      CVE-2025-40070 CVE-2025-40078 CVE-2025-40080 CVE-2025-40081                      CVE-2025-40084 CVE-2025-40085 CVE-2025-40087 CVE-2025-40088                      CVE-2025-40092 CVE-2025-40093 CVE-2025-40094 CVE-2025-40095                      CVE-2025-40096 CVE-2025-40099 CVE-2025-40100 CVE-2025-40103                      CVE-2025-40104 CVE-2025-40105 CVE-2025-40106 CVE-2025-40107                      CVE-2025-40109 CVE-2025-40111 CVE-2025-40112 CVE-2025-40115                      CVE-2025-40116 CVE-2025-40118 CVE-2025-40120 CVE-2025-40121                      CVE-2025-40123 CVE-2025-40124 CVE-2025-40125 CVE-2025-40126                      CVE-2025-40127 CVE-2025-40134 CVE-2025-40140 CVE-2025-40141                      CVE-2025-40153 CVE-2025-40154 CVE-2025-40156 CVE-2025-40167                      CVE-2025-40171 CVE-2025-40173 CVE-2025-40176 CVE-2025-40178                      CVE-2025-40179 CVE-2025-40183 CVE-2025-40186 CVE-2025-40187                      CVE-2025-40188 CVE-2025-40190 CVE-2025-40193 CVE-2025-40194                      CVE-2025-40197 CVE-2025-40198 CVE-2025-40200 CVE-2025-40201                      CVE-2025-40202 CVE-2025-40204 CVE-2025-40205 CVE-2025-40207

    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.158-1~deb11u1.  This version additionally includes many more bug     fixes from stable updates 6.1.154-6.1.158.

    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.

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

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6053-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     November 11, 2025                     https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2025-21861 CVE-2025-39929 CVE-2025-39931 CVE-2025-39934                      CVE-2025-39937 CVE-2025-39938 CVE-2025-39942 CVE-2025-39943                      CVE-2025-39944 CVE-2025-39945 CVE-2025-39946 CVE-2025-39949                      CVE-2025-39951 CVE-2025-39953 CVE-2025-39955 CVE-2025-39957                      CVE-2025-39964 CVE-2025-39967 CVE-2025-39968 CVE-2025-39969                      CVE-2025-39970 CVE-2025-39971 CVE-2025-39972 CVE-2025-39973                      CVE-2025-39977 CVE-2025-39978 CVE-2025-39980 CVE-2025-39982                      CVE-2025-39985 CVE-2025-39986 CVE-2025-39987 CVE-2025-39988                      CVE-2025-39993 CVE-2025-39994 CVE-2025-39995 CVE-2025-39996                      CVE-2025-39998 CVE-2025-40001 CVE-2025-40006 CVE-2025-40008                      CVE-2025-40010 CVE-2025-40011 CVE-2025-40013 CVE-2025-40018                      CVE-2025-40019 CVE-2025-40020 CVE-2025-40021 CVE-2025-40022                      CVE-2025-40026 CVE-2025-40027 CVE-2025-40029 CVE-2025-40030                      CVE-2025-40032 CVE-2025-40035 CVE-2025-40036 CVE-2025-40040                      CVE-2025-40042 CVE-2025-40043 CVE-2025-40044 CVE-2025-40048                      CVE-2025-40049 CVE-2025-40051 CVE-2025-40053 CVE-2025-40055                      CVE-2025-40056 CVE-2025-40060 CVE-2025-40062 CVE-2025-40068                      CVE-2025-40070 CVE-2025-40078 CVE-2025-40080 CVE-2025-40081                      CVE-2025-40084 CVE-2025-40085 CVE-2025-40087 CVE-2025-40088                      CVE-2025-40092 CVE-2025-40093 CVE-2025-40094 CVE-2025-40095                      CVE-2025-40096 CVE-2025-40099 CVE-2025-40100 CVE-2025-40103                      CVE-2025-40104 CVE-2025-40105 CVE-2025-40106 CVE-2025-40107                      CVE-2025-40109

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

    For the oldstable distribution (bookworm), these problems have been fixed     in version 6.1.158-1.

    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 Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

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.

An update of the linux package has been released.

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

  - net/9p: fix double req put in p9_fd_cancelled Syzkaller reports a KASAN issue as below: general protection     fault, probably for non-canonical address 0xfbd59c0000000021: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN:
    maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f] CPU: 0 PID: 5083 Comm: syz-     executor.2 Not tainted 6.1.134-syzkaller-00037-g855bd1d7d838 #0 Hardware name: QEMU Standard PC (i440FX +     PIIX, 1996), BIOS 1.12.0-1 04/01/2014 RIP: 0010:__list_del include/linux/list.h:114 [inline] RIP:
    0010:__list_del_entry include/linux/list.h:137 [inline] RIP: 0010:list_del include/linux/list.h:148     [inline] RIP: 0010:p9_fd_cancelled+0xe9/0x200 net/9p/trans_fd.c:734 Call Trace: <TASK>     p9_client_flush+0x351/0x440 net/9p/client.c:614 p9_client_rpc+0xb6b/0xc70 net/9p/client.c:734     p9_client_version net/9p/client.c:920 [inline] p9_client_create+0xb51/0x1240 net/9p/client.c:1027     v9fs_session_init+0x1f0/0x18f0 fs/9p/v9fs.c:408 v9fs_mount+0xba/0xcb0 fs/9p/vfs_super.c:126     legacy_get_tree+0x108/0x220 fs/fs_context.c:632 vfs_get_tree+0x8e/0x300 fs/super.c:1573 do_new_mount     fs/namespace.c:3056 [inline] path_mount+0x6a6/0x1e90 fs/namespace.c:3386 do_mount fs/namespace.c:3399     [inline] __do_sys_mount fs/namespace.c:3607 [inline] __se_sys_mount fs/namespace.c:3584 [inline]
    __x64_sys_mount+0x283/0x300 fs/namespace.c:3584 do_syscall_x64 arch/x86/entry/common.c:51 [inline]     do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 This happens     because of a race condition between: - The 9p client sending an invalid flush request and later cleaning     it up; - The 9p client in p9_read_work() canceled all pending requests. Thread 1 Thread 2 ...
    p9_client_create() ... p9_fd_create() ... p9_conn_create() ... // start Thread 2 INIT_WORK(&m->rq,     p9_read_work); p9_read_work() ... p9_client_rpc() ... ... p9_conn_cancel() ... spin_lock(&m->req_lock);
    ... p9_fd_cancelled() ... ... spin_unlock(&m->req_lock); // status rewrite p9_client_cb(m->client, req,     REQ_STATUS_ERROR) // first remove list_del(&req->req_list); ... spin_lock(&m->req_lock) ... // second     remove list_del(&req->req_list); spin_unlock(&m->req_lock) ... Commit 74d6a5d56629 (9p/trans_fd: Fix     concurrency del of req_list in p9_fd_cancelled/p9_read_work) fixes a concurrency issue in the 9p     filesystem client where the req_list could be deleted simultaneously by both p9_read_work and     p9_fd_cancelled functions, but for the case where req->status equals REQ_STATUS_RCVD. Update the check for     req->status in p9_fd_cancelled to skip processing not just received requests, but anything that is not     SENT, as whatever changed the state from SENT also removed the request from its list. Found by Linux     Verification Center (linuxtesting.org) with Syzkaller. [updated the check from status == RECV || status ==     ERROR to status != SENT] (CVE-2025-40027)

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

ID	Name	Product	Family	Severity
276782	Debian dla-4379 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	medium
274816	Debian dsa-6053 : affs-modules-6.1.0-37-4kc-malta-di - security update	Nessus	Debian Local Security Checks	medium
274526	Photon OS 4.0: Linux PHSA-2025-4.0-0899	Nessus	PhotonOS Local Security Checks	medium
271872	Linux Distros Unpatched Vulnerability : CVE-2025-40027	Nessus	Misc.	medium

Detections

Analytics

CVE-2025-40027

medium

Tenable Plugins

medium

medium

medium

medium