CVE Intelligence
Unknown

CVE-2026-98911 — dpaa2-switch: fix the error path in dpaa2_switch_rx()

In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: fix the error path in dpaa2_switch_rx() In case of an error in dpaa2_switch_rx(), the dpaa2_switch_free_fd() function is called in order to free the FD. This is incorrect since the dpaa2_switch_free_fd() is intended to be used on Tx frame descriptors, meaning that it expects in the software annotation area of the FD data to find a valid skb pointer on which to call dev_kfree_skb(). Fix this by extracting the dma_unmap_page() from dpaa2_switch_build_linear_skb() directly into the dpaa2_switch_rx() function. This allows us to directly use free_pages() in case of an error before an SKB was created and kfree_skb() afterwards.

Published Oct 23, 2026 · Updated Oct 23, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 791068c962469af0090e1a1ee63657fb9eef40db≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < ee54f8d7e642c44cfcc2dcb390b4c50e145d81b8≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 259ad6093204b999d41e7e6d0ad90ef9a71a44ab≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < f4ceb8e3d6d5becb4cda7a7098a8638e18c835a1≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < fa232b4496cb59503ae5108c756cbe10e59b0bc3≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 74c1c9f5c0c30bbd0c2cf87b6e3507e7ea46c13d< 5.15.222< 6.1.189
and 4 more < 6.6.158< 6.12.111< 6.18.53versions not specified by the source
Vulnerable CVE Program (cve.org) e CISA ADP

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Published → Received
    Oct 23, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 23, 2026
  • Source status changed · → Published
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 23, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

6 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-99087 dm-integrity: fix NULL pointer dereference when the 'R' flag is used 13h
  • CVE-2026-99086 dm-integrity: validate the superblock on resume 13h
  • CVE-2026-99084 readdir: take no inode lock on an immutable directory 13h
  • CVE-2026-99079 net/mlx5e: Prevent stale XSK buffer release on refill retry 13h
  • CVE-2026-99080 fs: Free any excess xarray nodes in clear_inode() 13h
  • CVE-2026-99081 bnxt_en: fix DMA mapping length for padded small packets 13h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98911 is "dpaa2-switch: fix the error path in dpaa2_switch_rx()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.