LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50564: s390/netiucv: Fix return type of netiucv_tx()

In the Linux kernel, the following vulnerability has been resolved: s390/netiucv: Fix return type of netiucv_tx() With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed. A proposed warning in clang aims to catch these at compile time, which reveals: drivers/s390/net/netiucv.c:1854:21: error: incompatible function pointer types initializing 'netdev_tx_t (*)(struct sk_buff *, struct net_device *)' (aka 'enum netdev_tx (*)(struct sk_buff *, struct net_device *)') with an expression of type 'int (struct sk_buff *, struct net_device *)' [-Werror,-Wincompatible-function-pointer-types-strict] .ndo_start_xmit = netiucv_tx, ^~~~~~~~~~ ->ndo_start_xmit() in 'struct net_device_ops' expects a return type of 'netdev_tx_t', not 'int'. Adjust the return type of netiucv_tx() to match the prototype's to resolve the warning and potential CFI failure, should s390 select ARCH_SUPPORTS_CFI_CLANG in the future. Additionally, while in the area, remove a comment block that is no longer relevant.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50564 is a Linux kernel issue in the s390 netiucv driver. A function used the wrong return type, which could trigger kernel control-flow integrity failures if that protection is enabled for s390. The described impact is a kernel panic or killed thread, not confirmed remote compromise.

Executive priority

Track and remediate through normal kernel maintenance unless s390 netiucv is business-critical. There is no source-supported evidence of active exploitation, but affected systems could face stability impact under relevant kernel configurations.

Technical view

netiucv_tx() was declared as returning int but assigned to ndo_start_xmit, which expects netdev_tx_t. With clang kCFI, indirect call target prototype mismatches can fail at runtime. The kernel fix changes the return type to match the net_device_ops prototype.

Likely exposure

Exposure appears limited to Linux systems using the s390 architecture and the netiucv driver in affected kernel ranges. The source lists Linux kernel versions from 2.6.32 through 6.2 as affected, with multiple stable-branch commits referenced.

Exploitation context

The sources do not report active exploitation, public exploit code, or KEV listing. The issue is described as a type mismatch that may cause CFI runtime failure if s390 supports CONFIG_CFI_CLANG in the future.

Researcher notes

This CVE appears to formalize a correctness fix for a function pointer prototype mismatch. The main security relevance is kCFI enforcement causing runtime failure, not a documented privilege escalation or data exposure path. CVSS and CWE are not provided in the source bundle.

Mitigation direction

  • Apply the relevant Linux stable kernel update containing the referenced netiucv fix.
  • If using vendor kernels, check distribution advisories for backported fixes.
  • Prioritize s390 systems using netiucv or custom kernels built with clang CFI considerations.

Validation and detection

  • Inventory Linux systems running on s390 architecture.
  • Check whether the netiucv driver is present or in use.
  • Compare kernel version and vendor backport status against referenced stable commits.
  • Review kernel build configuration for clang CFI-related options where applicable.
Prepared
Confidence
high
Sources
6

Public sources used

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-2022-50564 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdc1f8bf68b311b1537cb65893430b6796118498a, dc1f8bf68b311b1537cb65893430b6796118498a, dc1f8bf68b311b1537cb65893430b6796118498a, dc1f8bf68b311b1537cb65893430b6796118498a, dc1f8bf68b311b1537cb65893430b6796118498a, dc1f8bf68b311b1537cb65893430b6796118498a, dc1f8bf68b311b1537cb65893430b6796118498a, dc1f8bf68b311b1537cb65893430b6796118498a, dc1f8bf68b311b1537cb65893430b6796118498aunaffected
LinuxLinux2.6.32, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.