Kernel memory disclosure or crash via metadata miscast
Published May 21, 2024 · Updated Aug 5, 2026
Out-of-bounds read in Linux tunnel metadata handling allows local users to disclose kernel memory or crash the system. skb_tunnel_info() treats lwtstate->data as ip_tunnel_info without validating the metadata type, so VXLAN reads beyond an incompatible MPLS encapsulation object. Triggering the flaw requires local low-privileged access and a routing path that passes MPLS lightweight-tunnel metadata into VXLAN transmission.
Summary
What happened
Out-of-bounds read in Linux tunnel metadata handling allows local users to disclose kernel memory or crash the system. skb_tunnel_info() treats lwtstate->data as ip_tunnel_info without validating the metadata type, so VXLAN reads beyond an incompatible MPLS encapsulation object. Triggering the flaw requires local low-privileged access and a routing path that passes MPLS lightweight-tunnel metadata into VXLAN transmission.
The record
- CVE
- CVE-2021-47309
- Published
- May 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.3
- Affected versionversion=61adedf3e3f1d3f032c5a6a299978d91eff6d555 <2179d96ec702cc33ead02a9ce40ece599b8538c5
- Affected versionversion=61adedf3e3f1d3f032c5a6a299978d91eff6d555 <67a9c94317402b826fc3db32afc8f39336803d97
- Affected versionversion=61adedf3e3f1d3f032c5a6a299978d91eff6d555 <83bdcfbd968bcc91a0632b7b625e4a9b0cba5e0d
- Affected versionversion=61adedf3e3f1d3f032c5a6a299978d91eff6d555 <8aa13a86964cdec4fd969ef677c6614ff068641a
- Affected versionversion=61adedf3e3f1d3f032c5a6a299978d91eff6d555 <8bb1589c89e61e3b182dd546f1021928ebb5c2a6
- Affected versionversion=61adedf3e3f1d3f032c5a6a299978d91eff6d555 <a915379594f1e045421635c6316d8f3ffa018c58
- Affected versionversion=61adedf3e3f1d3f032c5a6a299978d91eff6d555 <b61d327cd3cc5ea591f3bf751dd11e034f388bb5
- Affected versionversion=61adedf3e3f1d3f032c5a6a299978d91eff6d555 <e7f3c9df40515a6c6b46f36c4c94cf48a043f887
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo