CVE-2022-50564

s390/netiucv: Fix return type of netiucv_tx()

N/A
Published: October 22, 2025 at 01:23 PM UTC
Updated: June 17, 2026 at 05:23 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.32 ≤ v < 4.14.3032.6.32 ≤ v < 4.19.2702.6.32 ≤ v < 4.9.3372.6.32 ≤ v < 5.10.1632.6.32 ≤ v < 5.15.862.6.32 ≤ v < 5.4.2292.6.32 ≤ v < 6.0.162.6.32 ≤ v < 6.1.22.6.32 ≤ v < 6.22.6.32dc1f8bf68b311b1537cb65893430b6796118498a
Vendor states this is fixed in 3ac0217ca9186c2f9af9a0113a331a42aa847894 (fixed)
Vendor states this is fixed in 4bee3c75d5bf7c2b5dc0b520410eb40449e5da31 (fixed)
Vendor states this is fixed in 85d392710275355425df8618ccbebbc336f5acc5 (fixed)
Vendor states this is fixed in 88d86d18d7cf7e9137c95f9d212bb9fff8a1b4be (fixed)
Vendor states this is fixed in d034fa43af92fc46a81d882f46d9cc3e4ffdbbcc (fixed)
Vendor states this is fixed in dfbf0122ea1b9b3e73fa22c8ff6bd888935c54fc (fixed)
Vendor states this is fixed in e7a849f740e3576e79cba403697e916f4c3a6f12 (fixed)
Vendor states this is fixed in eccc88c0efe407e579291792ad07a7dedc0f63f0 (fixed)
Vendor states this is fixed in f13d870fce90f01cf930bfaffecc8185ae0be21c (fixed)
Vendor states this is fixed in 2.6.32 (unaffected)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card