CVE-2022-50564: In the Linux kernel, the following vulnerability has been resolved: s390/netiucv: Fix return type of netiucv_tx() With clang's kernel control flow i...

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.

Metrics

EPSS Probability

0.23%

13.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= dc1f8bf68b311b1537cb65893430b6796118498a, < f13d870fce90f01cf930bfaffecc8185ae0be21c; >= dc1f8bf68b311b1537cb65893430b6796118498a, < eccc88c0efe407e579291792ad07a7dedc0f63f0; >= dc1f8bf68b311b1537cb65893430b6796118498a, < 85d392710275355425df8618ccbebbc336f5acc5; >= dc1f8bf68b311b1537cb65893430b6796118498a, < 4bee3c75d5bf7c2b5dc0b520410eb40449e5da31; >= dc1f8bf68b311b1537cb65893430b6796118498a, < 3ac0217ca9186c2f9af9a0113a331a42aa847894; >= dc1f8bf68b311b1537cb65893430b6796118498a, < dfbf0122ea1b9b3e73fa22c8ff6bd888935c54fc; >= dc1f8bf68b311b1537cb65893430b6796118498a, < e7a849f740e3576e79cba403697e916f4c3a6f12; >= dc1f8bf68b311b1537cb65893430b6796118498a, < d034fa43af92fc46a81d882f46d9cc3e4ffdbbcc; >= dc1f8bf68b311b1537cb65893430b6796118498a, < 88d86d18d7cf7e9137c95f9d212bb9fff8a1b4be
Linux	Linux	2.6.32

References

Timeline

Published: Oct 22, 2025
Last Modified: Jun 17, 2026
Status: Deferred

Frequently Asked Questions

What is CVE-2022-50564?

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.

How severe is CVE-2022-50564?

Severity scoring for CVE-2022-50564 is pending analysis. The EPSS model estimates a 0.23% probability of exploitation in the next 30 days.

How do I fix CVE-2022-50564?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2022

View all 2022CVEs →