In the Linux kernel, the following vulnerability has been resolved:
xen-netfront: Add missing skb_mark_for_recycle
Notice that skb_mark_for_recycle() is introduced later than fixes tag in
commit 6a5bcd84e886 ("page_pool: Allow drivers to hint on SKB recycling").
It is believed that fixes tag were missing a call to page_pool_release_page()
between v5.9 to v5.14, after which is should have used skb_mark_for_recycle().
Since v6.6 the call page_pool_release_page() were removed (in
commit 535b9c61bdef ("net: page_pool: hide page_pool_release_page()")
and remaining callers converted (in commit 6bfef2ec0172 ("Merge branch
'net-page_pool-remove-page_pool_release_page'")).
This leak became visible in v6.8 via commit dba1b8a7ab68 ("mm/page_pool: catch
page_pool memory leaks").
Security readout for executives and security teams
Plain-English summary
A missing Linux Xen network-driver recycling call can leak memory while processing network traffic. Sustained leakage may exhaust memory and disrupt an affected Xen guest, creating an availability risk. The supplied CVSS score is 7.5; no confidentiality or integrity impact is identified.
Executive priority
Treat this as a high-priority availability issue for Xen-based Linux workloads, especially exposed or memory-constrained guests. Inventory promptly and schedule supported kernel updates. Emergency response is not justified by the supplied evidence because active exploitation is unconfirmed.
Technical view
The xen-netfront driver failed to correctly return page-pool-backed packet buffers for recycling. Older kernels required page_pool_release_page(); later kernels required skb_mark_for_recycle(). The defect spans changing page-pool APIs and became more visible in Linux 6.8 after added leak detection. The supplied assessment indicates network-reachable, low-complexity denial of service without privileges or user interaction.
Likely exposure
Exposure is most likely where Linux runs as a Xen guest and uses xen-netfront. The record identifies affected releases beginning with 5.9 and lists 5.15.154, 6.1.85, 6.6.26, 6.8.5, and 6.9. Distribution backports may change actual status, so version strings alone are insufficient.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public exploit. CVSS describes a network-originated availability attack, but the source bundle does not document practical attack conditions, required traffic volume, or observed incidents.
Researcher notes
The fixes account for page-pool API evolution: release-page handling was needed in earlier branches, while later branches use skb_mark_for_recycle(). Linux 6.8 leak detection exposed the condition more clearly rather than necessarily introducing it. The affected-version representation is ambiguous; validate commit ancestry and distributor backports instead of relying only on release numbers.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable upstream xen-netfront fix.
Confirm distribution backport status against the five referenced Linux stable commits.
Prioritize Internet-facing or untrusted-network Xen guests with constrained memory.
Monitor affected guests until upgrades are completed and investigate unexplained memory growth or availability loss.
Validation and detection
Confirm whether each workload is a Xen guest using the xen-netfront driver.
Record running kernel versions and distribution package revisions.
Verify the installed kernel includes the relevant stable fix or documented vendor backport.
Review kernel logs for page-pool leak diagnostics, especially on Linux 6.8-era systems.
Compare guest memory consumption under normal network workloads before and after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-27393 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.