Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel correctness issue in the IBM s390 LCS network driver. The driver used a function return type that did not match the kernel networking interface. Under clang kernel CFI, that mismatch could trigger a runtime failure such as a kernel panic. Exposure appears narrow and no active exploitation is reported in the provided sources.
Executive priority
Treat as a targeted maintenance item, not an emergency. Prioritize only if the organization runs Linux on IBM Z or s390 environments with LCS networking. Otherwise, track through normal kernel patch cycles.
Technical view
The s390 lcs_start_xmit() implementation returned int while net_device_ops.ndo_start_xmit expects netdev_tx_t. With CONFIG_CFI_CLANG, indirect call prototype validation can fail at runtime. The upstream fix changes the function return type to match the expected prototype. The CVE lists multiple affected Linux kernel branches and stable commit references.
Likely exposure
Most relevant to Linux systems on s390/s390x using the LCS network driver, especially kernels built with clang kCFI. General Linux fleets without s390 LCS exposure are unlikely to be affected based on the provided description.
Exploitation context
The provided sources do not report exploitation, public exploit activity, or KEV listing. The described impact is a potential CFI runtime failure, not a documented remote compromise path. Evidence points to a configuration- and architecture-specific stability risk.
Researcher notes
The CVE data gives no CVSS, CWE, or exploitation evidence. The issue is a type mismatch affecting CFI validation behavior. The description suggests s390 CFI support was prospective, so real-world impact depends on kernel branch, architecture, driver use, and build configuration.
Mitigation direction
- Check Linux distribution advisories for CVE-2022-50728 applicability and kernel updates.
- Update affected kernels to a release containing the referenced stable fix.
- Prioritize s390/s390x systems using the LCS network driver.
- If no vendor package is available, follow vendor kernel backport guidance.
Validation and detection
- Inventory Linux systems running on s390 or s390x architecture.
- Identify kernels in the affected version ranges from the CVE record.
- Confirm whether the LCS network driver is present or used.
- Verify the vendor kernel includes one of the referenced stable commits.
- Review kernel build configuration for clang kCFI relevance.
Public sources used
- CVE Program
- CVE List V5
- Linux stable commit 7b4da3fcd513
- Linux stable commit d49cc2b70571
- Linux stable commit e684215d8a90
- Linux stable commit 20022d551f20
- Linux stable commit ebc3c77785dc
- Linux stable commit 5ad774fb823c
- Linux stable commit 69669820844f
- Linux stable commit cda74cdc280b
- Linux stable commit bb16db839365
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2022-50728 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/7b4da3fcd513b8e67823eb80da37aad99b3339c1CVE reference
- https://git.kernel.org/stable/c/d49cc2b705711fb8fb849e7c660929b2100360b7CVE reference
- https://git.kernel.org/stable/c/e684215d8a903752e2b0cc946517fb61e57a880aCVE reference
- https://git.kernel.org/stable/c/20022d551f2064a194d8e0acb6cd7a85094a17b2CVE reference
- https://git.kernel.org/stable/c/ebc3c77785dc8b5b626309c0032a38fbb139287aCVE reference
- https://git.kernel.org/stable/c/5ad774fb823c24bbeb21a15a67103ea7a6f5b928CVE reference
- https://git.kernel.org/stable/c/69669820844f81a77b6db24b86581320ae4d17afCVE reference
- https://git.kernel.org/stable/c/cda74cdc280ba35c8993e7517bac5c257ff36f18CVE reference
- https://git.kernel.org/stable/c/bb16db8393658e0978c3f0d30ae069e878264fa3CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
