CVE-2024-27403: netfilter: nft_flow_offload: reset dst in route object after setting up flow
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_flow_offload: reset dst in route object after setting up flow
dst is transferred to the flow object, route object does not own it
anymore. Reset dst in route object, otherwise if flow_offload_add()
fails, error path releases dst twice, leading to a refcount underflow.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux netfilter flow offload can release the same routing reference twice when flow creation fails. A low-privileged local attacker may be able to damage kernel state, potentially affecting confidentiality, integrity, and availability. The supplied CVSS score is 7.8; remote exploitation is not indicated.
Executive priority
Treat as a high-priority operating-system update where untrusted users or workloads can execute locally. It is less urgent for systems without such access, but version ambiguity warrants prompt inventory and vendor confirmation. Internet exposure alone does not satisfy the documented local attack requirement.
Technical view
After dst ownership transfers to a flow object, the route object retains the reference. If flow_offload_add() fails, error handling releases dst again, causing a reference-count underflow. The vulnerability is local, low-complexity, requires low privileges, and needs no user interaction according to the supplied CVSS vector.
Likely exposure
Prioritize Linux systems using nftables flow offload and permitting untrusted local access. The supplied version data spans Linux 4.16 through 6.8 but lacks clear range semantics. Confirm affectedness using distribution advisories, kernel provenance, and the referenced stable fixes rather than version numbers alone.
Exploitation context
The supplied record does not establish active exploitation, and its KEV indicator is false. The CVSS vector describes local access with low privileges and low complexity, but the sources provide no evidence about public exploit reliability, observed attacks, or required runtime configuration.
Researcher notes
The defect is a lifetime-management error on an error path: dst ownership moves to the flow object, but the stale route reference enables a second release. Multiple stable-kernel commits indicate branch-specific backports. Exact vulnerable ranges and practical exploitability are not established by the supplied bundle.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix.
Check distribution security guidance for fixed package versions and required reboot instructions.
Prioritize multi-user systems and hosts permitting untrusted local code execution.
Reduce unnecessary untrusted local access while patching is pending.
Validation and detection
Inventory installed kernel versions, package revisions, and distribution backports.
Determine whether nftables flow offload is enabled or used.
Verify the installed kernel includes the applicable referenced stable fix.
Confirm patched systems booted into the updated kernel.
Monitor vendor advisories for corrected affected-version boundaries.
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-27403 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.