In the Linux kernel, the following vulnerability has been resolved: xfrm: delete x->tunnel as we delete x The ipcomp fallback tunnels currently get deleted (from the various lists and hashtables) as the last user state that needed that fallback is destroyed (not deleted). If a reference to that user state still exists, the fallback state will remain on the hashtables/lists, triggering the WARN in xfrm_state_fini. Because of those remaining references, the fix in commit f75a2804da39 ("xfrm: destroy xfrm_state synchronously on net exit path") is not complete. We recently fixed one such situation in TCP due to defered freeing of skbs (commit 9b6412e6979f ("tcp: drop secpath at the same time as we currently drop dst")). This can also happen due to IP reassembly: skbs with a secpath remain on the reassembly queue until netns destruction. If we can't guarantee that the queues are flushed by the time xfrm_state_fini runs, there may still be references to a (user) xfrm_state, preventing the timely deletion of the corresponding fallback state. Instead of chasing each instance of skbs holding a secpath one by one, this patch fixes the issue directly within xfrm, by deleting the fallback state as soon as the last user state depending on it has been deleted. Destruction will still happen when the final reference is dropped. A separate lockdep class for the fallback state is required since we're going to lock x->tunnel while x is locked.

The remote Oracle Linux 10 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2025-28066 advisory.

    - fs/proc: fix uaf in proc_readdir_de() (Wei Yang)   {CVE-2025-40271}

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

  - xfrm: delete x->tunnel as we delete x The ipcomp fallback tunnels currently get deleted (from the various     lists and hashtables) as the last user state that needed that fallback is destroyed (not deleted). If a     reference to that user state still exists, the fallback state will remain on the hashtables/lists,     triggering the WARN in xfrm_state_fini. Because of those remaining references, the fix in commit     f75a2804da39 (xfrm: destroy xfrm_state synchronously on net exit path) is not complete. We recently     fixed one such situation in TCP due to defered freeing of skbs (commit 9b6412e6979f (tcp: drop secpath at     the same time as we currently drop dst)). This can also happen due to IP reassembly: skbs with a secpath     remain on the reassembly queue until netns destruction. If we can't guarantee that the queues are flushed     by the time xfrm_state_fini runs, there may still be references to a (user) xfrm_state, preventing the     timely deletion of the corresponding fallback state. Instead of chasing each instance of skbs holding a     secpath one by one, this patch fixes the issue directly within xfrm, by deleting the fallback state as     soon as the last user state depending on it has been deleted. Destruction will still happen when the final     reference is dropped. A separate lockdep class for the fallback state is required since we're going to     lock x->tunnel while x is locked. (CVE-2025-40215)

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

ID	Name	Product	Family	Severity
296481	SUSE SLES15 Security Update : kernel (SUSE-SU-2026:0278-1)	Nessus	SuSE Local Security Checks	high
279590	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2025-28066)	Nessus	Oracle Linux Local Security Checks	medium
277482	Linux Distros Unpatched Vulnerability : CVE-2025-40215	Nessus	Misc.	medium

Detections

Analytics

CVE-2025-40215

medium

Tenable Plugins

high

medium

medium