CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain
Remove netdevice from inet/ingress basechain in case NETDEV_UNREGISTER
event is reported, otherwise a stale reference to netdevice remains in
the hook list.
Security readout for executives and security teams
Plain-English summary
A Linux kernel netfilter flaw can leave a deleted network device referenced by an ingress filtering chain. A local, low-privileged attacker may be able to trigger unsafe kernel behavior, potentially compromising confidentiality, integrity, and availability. Systems running affected kernels should receive updated vendor kernel packages promptly.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially on shared or locally accessible Linux systems. It is not described as remotely exploitable, and active exploitation is not substantiated. Schedule expedited vendor kernel updates, with normal testing and reboot coordination, rather than emergency internet-wide isolation.
Technical view
When an inet/ingress nftables base chain receives a NETDEV_UNREGISTER event, the vulnerable kernel fails to remove the associated netdevice from its hook list. The resulting stale reference can create unsafe kernel memory behavior. The supplied CVSS 3.1 assessment is 7.8: local access, low complexity, low privileges, no user interaction, and high potential impact.
Likely exposure
Exposure requires an affected Linux kernel and the relevant netfilter inet/ingress base-chain behavior. The bundle identifies affected releases including 5.10, 5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3, and 6.8. Distribution backports may change actual status, so version strings alone are insufficient.
Exploitation context
The supplied CVSS indicates local, low-privileged access rather than remote exploitation. The bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation or public weaponization. Exploitability details beyond the stale netdevice reference are not established by the supplied sources.
Researcher notes
The central defect is lifecycle handling: NETDEV_UNREGISTER does not remove the netdevice from an inet/ingress base chain's hook list. Multiple stable-kernel commits are supplied, suggesting branch-specific fixes. The affected-version data contains duplicate commit identifiers and ambiguous entries; determine remediation from distribution advisories and package backport records.
Mitigation direction
Install a vendor-supported kernel package containing the applicable upstream fix.
Check distribution security guidance because vendors may backport fixes without changing major kernel versions.
Prioritize multi-user systems where untrusted users can obtain local low-privileged access.
Restrict unnecessary local accounts while kernel updates are being validated and deployed.
Validation and detection
Inventory running kernel versions across Linux hosts and compare them with vendor advisories.
Verify installed kernel package changelogs identify CVE-2024-26808 or the applicable upstream fix.
Confirm hosts rebooted into the remediated kernel after package installation.
Review relevant nftables configurations for inet ingress base chains when prioritizing exposure.
Re-scan deployed hosts after remediation and investigate remaining affected-version findings.
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-26808 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.