cbcvebase.
CVE-2022-50728
published 2025-12-24

CVE-2022-50728: 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…

PriorityP422low5.5
EPSS
0.25%
16.1th percentile
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.

Affected

23 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.4-1 (bookworm)linux 6.1.4-1 (bookworm)
linuxlinux
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < 7b4da3fcd513b8e67823eb80da37aad99b3339c17b4da3fcd513b8e67823eb80da37aad99b3339c1
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < d49cc2b705711fb8fb849e7c660929b2100360b7d49cc2b705711fb8fb849e7c660929b2100360b7
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < e684215d8a903752e2b0cc946517fb61e57a880ae684215d8a903752e2b0cc946517fb61e57a880a
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < 20022d551f2064a194d8e0acb6cd7a85094a17b220022d551f2064a194d8e0acb6cd7a85094a17b2
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < ebc3c77785dc8b5b626309c0032a38fbb139287aebc3c77785dc8b5b626309c0032a38fbb139287a
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < 5ad774fb823c24bbeb21a15a67103ea7a6f5b9285ad774fb823c24bbeb21a15a67103ea7a6f5b928
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < 69669820844f81a77b6db24b86581320ae4d17af69669820844f81a77b6db24b86581320ae4d17af
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < cda74cdc280ba35c8993e7517bac5c257ff36f18cda74cdc280ba35c8993e7517bac5c257ff36f18
linuxlinux>= dc1f8bf68b311b1537cb65893430b6796118498a < bb16db8393658e0978c3f0d30ae069e878264fa3bb16db8393658e0978c3f0d30ae069e878264fa3
linuxlinux_kernel>= 0 < 5.10.178-15.10.178-1
linuxlinux_kernel>= 0 < 6.1.4-16.1.4-1
linuxlinux_kernel>= 0 < 6.1.4-16.1.4-1
linuxlinux_kernel>= 0 < 6.1.4-16.1.4-1
linuxlinux_kernel>= 2.6.32 < 4.9.3374.9.337
linuxlinux_kernel>= 4.10.0 < 4.14.3034.14.303
linuxlinux_kernel>= 4.15.0 < 4.19.2704.19.270
linuxlinux_kernel>= 4.20.0 < 5.4.2295.4.229
linuxlinux_kernel>= 5.11.0 < 5.15.865.15.86
linuxlinux_kernel>= 5.16.0 < 6.0.166.0.16
linuxlinux_kernel>= 5.5.0 < 5.10.1635.10.163
linuxlinux_kernel>= 6.1.0 < 6.1.26.1.2
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.