LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23013: net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback

In the Linux kernel, the following vulnerability has been resolved: net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback octep_vf_request_irqs() requests MSI-X queue IRQs with dev_id set to ioq_vector. If request_irq() fails part-way, the rollback loop calls free_irq() with dev_id set to 'oct', which does not match the original dev_id and may leave the irqaction registered. This can keep IRQ handlers alive while ioq_vector is later freed during unwind/teardown, leading to a use-after-free or crash when an interrupt fires. Fix the error path to free IRQs with the same ioq_vector dev_id used during request_irq().

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux network driver can leave an interrupt handler active after a partial setup failure. Later cleanup may free memory still referenced by that handler, potentially causing a kernel crash or use-after-free when an interrupt occurs. Risk is concentrated in systems using the octeon_ep_vf driver, not Linux systems generally.

Executive priority

Prioritize remediation on systems actively using octeon_ep_vf, especially critical network infrastructure where kernel crashes would disrupt service. Treat other Linux systems as lower priority after confirming the driver is absent. Evidence supports a serious local flaw, but not active exploitation or broad remote exposure.

Technical view

octep_vf_request_irqs() registers MSI-X queue interrupts using ioq_vector as dev_id. Its rollback path incorrectly passed oct to free_irq(), so the irqaction could remain registered. Subsequent teardown may free ioq_vector, creating a use-after-free when the retained handler runs. The published correction uses the matching ioq_vector identifier during rollback.

Likely exposure

Exposure requires an affected Linux kernel, use of the octeon_ep_vf network driver, and a partial IRQ-registration failure that reaches the faulty rollback path. The bundle marks Linux versions including 6.9, 6.12.67, 6.18.7, and 6.19 as affected, but exact distribution package status is not provided.

Exploitation context

The supplied CVSS 3.1 score is 7.0: local access, high complexity, low privileges, and no user interaction. CISA KEV status is false, and the provided sources do not report active exploitation or a public exploit. Confidentiality, integrity, and availability impacts are rated high, although the description specifically demonstrates use-after-free or crash potential.

Researcher notes

The vulnerable condition is an error-path lifetime mismatch, not the normal successful IRQ setup path. Practical reachability depends on inducing or encountering a partial request_irq() failure and a later interrupt. The bundle provides three stable-kernel corrections but does not map each commit to a specific release or distribution package.

Mitigation direction

  • Identify hosts using the octeon_ep_vf driver and prioritize those systems.
  • Check distribution or kernel vendor advisories for package-specific affected and fixed versions.
  • Upgrade to a vendor-supported kernel containing the referenced upstream correction.
  • Apply normal kernel maintenance controls until affected hosts can be updated.

Validation and detection

  • Record running kernel and distribution package versions on systems using the driver.
  • Confirm package status against the relevant distribution or kernel vendor advisory.
  • Verify the installed kernel includes the matching-dev_id rollback correction.
  • After updating, reboot into the corrected kernel and confirm the active version.
Prepared
Confidence
high
Sources
5

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-2026-23013 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7High
CVSS 3.1 vector shape for CVE-2026-23013Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1cd3b407977c3ab1d2ddc26cb7113e7fb1509cd1, 1cd3b407977c3ab1d2ddc26cb7113e7fb1509cd1, 1cd3b407977c3ab1d2ddc26cb7113e7fb1509cd1unaffected
LinuxLinux6.9, 0, 6.12.67, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.