CVE-2024-27030: octeontx2-af: Use separate handlers for interrupts
In the Linux kernel, the following vulnerability has been resolved:
octeontx2-af: Use separate handlers for interrupts
For PF to AF interrupt vector and VF to AF vector same
interrupt handler is registered which is causing race condition.
When two interrupts are raised to two CPUs at same time
then two cores serve same event corrupting the data.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux octeontx2-af network driver can let two processor cores handle the same device event simultaneously, potentially corrupting kernel-managed data. Exploitation requires local access with low privileges and a system using the affected driver path. Successful abuse could compromise confidentiality, integrity, and availability.
Executive priority
Treat this as high priority for infrastructure using the affected OcteonTX2 driver path because successful local abuse may affect all three security objectives. Scope hardware and driver usage promptly, then patch confirmed exposures through normal emergency procedures. Broader Linux fleets should be assessed before assuming universal exposure.
Technical view
The octeontx2-af driver used one handler for PF-to-AF and VF-to-AF interrupt vectors. Simultaneous interrupts on separate CPUs could make both cores process the same event, corrupting data. The CVSS 3.1 score is 7.8: local, low-complexity, low-privilege access without user interaction. Referenced stable commits separate the handlers.
Likely exposure
Exposure is likely concentrated on affected Linux kernels using the octeontx2-af driver and associated PF/VF interrupt functionality. The supplied version list does not clearly express branch ranges or distribution backports. Systems without this driver path are not evidenced as exposed by the bundle.
Exploitation context
The supplied sources do not establish public or active exploitation, and the CVE is not marked as KEV. The CVSS vector describes a local attack requiring low privileges, not a remotely reachable flaw. Absence from KEV does not prove exploitation has never occurred.
Researcher notes
The sources describe a concurrency flaw but assign no CWE and provide no exploit evidence. Exact affected ranges are ambiguous in the flattened version data, so branch-specific stable commits and distribution backports require verification. Multiple upstream commits appear to provide equivalent fixes across maintained kernel branches.
Mitigation direction
Update to a vendor-supported kernel containing the applicable referenced stable fix.
Confirm distribution backports instead of relying solely on upstream kernel version numbers.
Prioritize systems where octeontx2-af and PF/VF virtualization functionality are active.
Follow vendor guidance; the supplied sources identify no configuration-only mitigation.
Validation and detection
Inventory kernel builds and identify systems using the octeontx2-af driver.
Verify each vendor kernel contains the applicable upstream fix or documented backport.
Test OcteonTX2 PF/VF-to-AF interrupt functionality after updating.
Review kernel and device logs for corruption or crashes, without treating them as proof of exploitation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-27030 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.