CVE-2022-50486
Last modified
CVE-2022-50486 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net: ethernet: ti: Fix return type of netcp_ndo_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. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net: ethernet: ti: Fix return type of netcp_ndo_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/net/ethernet/ti/netcp_core.c:1944: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 = netcp_ndo_start_xmit, ^~~~~~~~~~~~~~~~~~~~ 1 error generated. ->ndo_start_xmit() in 'struct net_device_ops' expects a return type of 'netdev_tx_t', not 'int'. Adjust the return type of netcp_ndo_start_xmit() to match the prototype's to resolve the warning and CFI failure.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.0, < 4.9.337 |
| Linux | Linux Kernel | >= 4.10, < 4.14.303 |
| Linux | Linux Kernel | >= 4.15, < 4.19.270 |
| Linux | Linux Kernel | >= 4.20, < 5.4.229 |
| Linux | Linux Kernel | >= 5.5, < 5.10.163 |
| Linux | Linux Kernel | >= 5.11, < 5.15.86 |
| Linux | Linux Kernel | >= 5.16, < 6.0.16 |
| Linux | Linux Kernel | >= 6.1, < 6.1.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-50486?
How severe is CVE-2022-50486?
How do I fix CVE-2022-50486?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-50480In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50481In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50482In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50483In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50484In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50485In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50487Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-50488In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50489In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50490In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-50491In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50492In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2022-50486?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
