CVE-2022-50728

s390/lcs: Fix return type of lcs_start_xmit()

State
Published
Severity
Not scored
Published
Dec 24, 2025
Updated
May 11, 2026
Reserved
Dec 24, 2025

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

s390/lcs: Fix return type of lcs_start_xmit()

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/lcs.c:2090: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 = lcs_start_xmit, ^~~~~~~~~~~~~~ drivers/s390/net/lcs.c:2097: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 = lcs_start_xmit, ^~~~~~~~~~~~~~

->ndo_start_xmit() in 'struct net_device_ops' expects a return type of 'netdev_tx_t', not 'int'. Adjust the return type of lcs_start_xmit() to match the prototype's to resolve the warning and potential CFI failure, should s390 select ARCH_SUPPORTS_CFI_CLANG in the future.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • dc1f8bf68b311b1537cb65893430b6796118498a to before 7b4da3fcd513b8e67823eb80da37aad99b3339c1Affected
  • dc1f8bf68b311b1537cb65893430b6796118498a to before d49cc2b705711fb8fb849e7c660929b2100360b7Affected
  • dc1f8bf68b311b1537cb65893430b6796118498a to before e684215d8a903752e2b0cc946517fb61e57a880aAffected
  • dc1f8bf68b311b1537cb65893430b6796118498a to before 20022d551f2064a194d8e0acb6cd7a85094a17b2Affected
  • dc1f8bf68b311b1537cb65893430b6796118498a to before ebc3c77785dc8b5b626309c0032a38fbb139287aAffected
  • dc1f8bf68b311b1537cb65893430b6796118498a to before 5ad774fb823c24bbeb21a15a67103ea7a6f5b928Affected
  • dc1f8bf68b311b1537cb65893430b6796118498a to before 69669820844f81a77b6db24b86581320ae4d17afAffected
  • dc1f8bf68b311b1537cb65893430b6796118498a to before cda74cdc280ba35c8993e7517bac5c257ff36f18Affected
  • dc1f8bf68b311b1537cb65893430b6796118498a to before bb16db8393658e0978c3f0d30ae069e878264fa3Affected
LinuxLinux
  • 2.6.32Affected
  • before 2.6.32Not affected
  • 4.9.337 through 4.9.*Not affected
  • 4.14.303 through 4.14.*Not affected
  • 4.19.270 through 4.19.*Not affected
  • 5.4.229 through 5.4.*Not affected
  • 5.10.163 through 5.10.*Not affected
  • 5.15.86 through 5.15.*Not affected
  • 6.0.16 through 6.0.*Not affected
  • 6.1.2 through 6.1.*Not affected
  • 6.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.