Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-41088: can: mcp251xfd: fix infinite loop when xmit fails

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3e72558c1711d524e3150103739ddd06650e291b, 6c6b4afa59c2fb4d1759235f866d8caed2aa4729, d8fb63e46c884c898a38f061c2330f7729e75510; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.47.1-1; azl3 kernel 6.6.47.1-1 on Azure Linux 3.0 6.6.47.1-1.

Low priority for now. Upgrade to Linux Linux 3e72558c1711d524e3150103739ddd06650e291b, 6c6b4afa59c2fb4d1759235f866d8caed2aa4729, d8fb63e46c884c898a38f061c2330f7729e75510; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.47.1-1; azl3 kernel 6.6.47.1-1 on Azure Linux 3.0 6.6.47.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: can: mcp251xfd: fix infinite loop when xmit fails When the mcp251xfd_start_xmit() function fails, the driver stops processing messages, and the interrupt routine does not return, running indefinitely even after killing the running application. Error messages: [ 441.298819] mcp251xfd spi2.0 can0: ERROR in mcp251xfd_start_xmit: -16 [ 441.306498] mcp251xfd spi2.0 can0: Transmit Event FIFO buffer not empty. (seq=0x000017c7, tef_tail=0x000017cf, tef_head=0x000017d0, tx_head=0x000017d3). ... and repeat forever. The issue can be triggered when multiple devices share the same SPI interface. And there is concurrent access to the bus. The problem occurs because tx_ring->head increments even if mcp251xfd_start_xmit() fails. Consequently, the driver skips one TX package while still expecting a response in mcp251xfd_handle_tefif_one(). Resolve the issue by starting a workqueue to write the tx obj synchronously if err = -EBUSY. In case of another error, decrement tx_ring->head, remove skb from the echo stack, and drop the message. [mkl: use more imperative wording in patch description]

Published
Jul 29, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-41088

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.10affected
    • 55e5b97f003e85e66babb55f357627d52081a264 and later · before f926c022ebaabf7963bebf89a97201d66978a025affected · git
    • 55e5b97f003e85e66babb55f357627d52081a264 and later · before 3e72558c1711d524e3150103739ddd06650e291baffected · git
    • 55e5b97f003e85e66babb55f357627d52081a264 and later · before 6c6b4afa59c2fb4d1759235f866d8caed2aa4729affected · git
    • 55e5b97f003e85e66babb55f357627d52081a264 and later · before d8fb63e46c884c898a38f061c2330f7729e75510affected · git
    • before 5.10not affected · semver
    • 6.1.97 and later · up to and including 6.1.*not affected · semver
    • 6.6.37 and later · up to and including 6.6.*not affected · semver
    • 6.9.8 and later · up to and including 6.9.*not affected · semver
    • 6.10 and laternot affected · original_commit_for_fix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.10 and later · before 6.1.97
  • linux linux kernel6.2 and later · before 6.6.37
  • linux linux kernel6.7 and later · before 6.9.8

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.98-16.1.98-1
Debian:13linuxbefore 6.9.8-16.9.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-41086Jul 29, 2024 · bcachefs: Fix sb_field_downgrade validation
    22Monitor
  • ← EarlierCVE-2024-41087Jul 29, 2024 · ata: libata-core: Fix double free on error
    31Monitor
  • Later →CVE-2024-41089Jul 29, 2024 · drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3e72558c1711d524e3150103739ddd06650e291bVendor (CNA)
Linux Linux6c6b4afa59c2fb4d1759235f866d8caed2aa4729Vendor (CNA)
Linux Linuxd8fb63e46c884c898a38f061c2330f7729e75510Vendor (CNA)
Linux Linuxf926c022ebaabf7963bebf89a97201d66978a025Vendor (CNA)
azl3 kernel 6.6.35.1-5 on Azure Linux 3.06.6.47.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.47.1-1 on Azure Linux 3.06.6.47.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.98-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-2703289 days apartf2fs: fix to avoid potential panic during recovery
    25Monitor
  • CVE-2022-4863592 days apartfsdax: Fix infinite loop in dax_iomap_rw()
    24Monitor
  • CVE-2024-422409 days apartx86/bhi: Avoid warning in #DB handler due to BHI mitigation
    22Monitor
  • CVE-2024-422469 days apartnet, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
    22Monitor
  • CVE-2022-4884013 days apartiavf: Fix hang during reboot/shutdown
    22Monitor
  • CVE-2022-4886213 days apartvhost: fix hung thread due to erroneous iotlb entries
    22Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records