CVE-2024-41091: tun: add missing verification for short frame
In the Linux kernel, the following vulnerability has been resolved:
tun: add missing verification for short frame
The cited commit missed to check against the validity of the frame length
in the tun_xdp_one() path, which could cause a corrupted skb to be sent
downstack. Even before the skb is transmitted, the
tun_xdp_one-->eth_type_trans() may access the Ethernet header although it
can be less than ETH_HLEN. Once transmitted, this could either cause
out-of-bound access beyond the actual length, or confuse the underlayer
with incorrect or inconsistent header length in the skb metadata.
In the alternative path, tun_get_user() already prohibits short frame which
has the length less than Ethernet header size from being transmitted for
IFF_TAP.
This is to drop any frame shorter than the Ethernet header size just like
how tun_get_user() does.
CVE: CVE-2024-41091
Security readout for executives and security teams
Plain-English summary
A low-privileged local user could submit an undersized Ethernet frame through an affected Linux TAP/XDP path. Missing length validation may corrupt network-buffer handling, leading to out-of-bounds access or inconsistent packet metadata. The supplied CVSS score is 8.8, reflecting potentially high confidentiality, integrity, and availability impact.
Executive priority
Treat this as a prompt patching priority for systems where lower-privileged local users can access TAP/XDP processing. Purely remote exposure is not supported by the supplied evidence. Escalate uncertain kernel builds to engineering because the provided affected-version representation is ambiguous.
Technical view
The tun_xdp_one() path failed to reject IFF_TAP frames shorter than ETH_HLEN before calling eth_type_trans(). This can create a corrupted skb, permit Ethernet-header access beyond the actual frame, or send inconsistent length metadata downstream. The resolution adds the same short-frame rejection already present in tun_get_user().
Likely exposure
Potentially exposed systems run a vulnerable Linux kernel and permit a low-privileged local actor to reach TAP/XDP processing. The bundle's flattened version list does not clearly distinguish affected ranges from correction boundaries, so exposure should not be inferred from version strings alone.
Exploitation context
The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction. The CVE is not listed in KEV, and no supplied source establishes active exploitation or a public exploit. This is absence of supporting evidence, not proof that exploitation has never occurred.
Researcher notes
The alternate tun_get_user() path already rejected undersized IFF_TAP frames; tun_xdp_one() lacked equivalent validation. The correction drops those frames before eth_type_trans(). No CWE is assigned. Practical reachability, distribution backports, and exact affected ranges require build-specific verification.
Mitigation direction
Apply vendor or distribution kernel updates incorporating the referenced stable-kernel correction.
Prioritize systems where low-privileged users can access TAP/XDP networking paths.
If updates are delayed, consult Linux or distribution guidance for supported mitigations; none are specified here.
Limit unnecessary local access to affected systems pending updates.
Validation and detection
Inventory running kernel builds and systems configured with TAP interfaces or XDP processing.
Compare each kernel build against distribution advisories and inclusion of the referenced correction.
Confirm updated systems were restarted into the corrected kernel.
Use authorized regression testing to confirm tun_xdp_one rejects frames shorter than the Ethernet header.
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-41091 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.