Kernel warning via unassociated PPP transmit skb
Published Dec 9, 2025 · Updated May 11, 2026
Improper namespace association in the Linux kernel PPP transmit path allows local users to trigger a flow-dissector warning through a PPP write. The ppp_send_frame function passes an skb with neither its device nor socket set, leaving the dissector without a network namespace; the fix assigns ppp->dev to skb->dev. Reachability requires local access to create and configure a PPP unit and transmit a frame, and the published evidence demonstrates a kernel warning rather than a crash or data compromise.
Summary
What happened
Improper namespace association in the Linux kernel PPP transmit path allows local users to trigger a flow-dissector warning through a PPP write. The ppp_send_frame function passes an skb with neither its device nor socket set, leaving the dissector without a network namespace; the fix assigns ppp->dev to skb->dev. Reachability requires local access to create and configure a PPP unit and transmit a frame, and the published evidence demonstrates a kernel warning rather than a crash or data compromise.
The record
- CVE
- CVE-2022-50655
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.20
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <148dcbd3af039ae39c3af697a3183008c7995805
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <18dc946360bfe0de016a59e3cc3ee1f450fceb9d
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <4b8f3b939266c90f03b7cc7e26a4c28c7b64137b
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <7da524781c531ebaf2f94c9dc4c541b82edecfed
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <9f225444467b98579cf28d94f4ad053460dfdb84
- Affected versionversion=d58e468b1112dcd1d5193c0a89ff9f98b5a3e8b9 <ee678b1f52f9439e930db2db3fd7e345d03e1a50
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Published PPP flow-dissector warning reproducerproof of concept · demonstrated
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