Local kernel panic via transmit callback mismatch
Published Dec 24, 2025 · Updated Dec 24, 2025
Incorrect callback typing in the s390 LCS driver in Linux allows local users to trigger a kernel panic or thread termination. The lcs_start_xmit function returns int although the net_device_ops ndo_start_xmit callback requires netdev_tx_t, so kCFI prototype validation rejects the indirect call. The failure requires CONFIG_CFI_CLANG and s390 architecture support for Clang kCFI; the reported consequence is limited to a panic or termination of the calling thread.
Summary
What happened
Incorrect callback typing in the s390 LCS driver in Linux allows local users to trigger a kernel panic or thread termination. The lcs_start_xmit function returns int although the net_device_ops ndo_start_xmit callback requires netdev_tx_t, so kCFI prototype validation rejects the indirect call. The failure requires CONFIG_CFI_CLANG and s390 architecture support for Clang kCFI; the reported consequence is limited to a panic or termination of the calling thread.
The record
- CVE
- CVE-2022-50728
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <20022d551f2064a194d8e0acb6cd7a85094a17b2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ad774fb823c24bbeb21a15a67103ea7a6f5b928
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <69669820844f81a77b6db24b86581320ae4d17af
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7b4da3fcd513b8e67823eb80da37aad99b3339c1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bb16db8393658e0978c3f0d30ae069e878264fa3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cda74cdc280ba35c8993e7517bac5c257ff36f18
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d49cc2b705711fb8fb849e7c660929b2100360b7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e684215d8a903752e2b0cc946517fb61e57a880a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ebc3c77785dc8b5b626309c0032a38fbb139287a
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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