Skip to main content
VulnerabilityPublished Updated

CVE-2026-98145: Linux kernel · Out-of-bounds Read

Source GCVE Database

0
Authoritative record:CVE-2026-98145· Medium

Not known to be exploited · CVSS 5.5 Medium : upgrade to ef6d27af71e1dc43181ec797a6aaa77c27c36786 or ed74e8d603df457bfcf16ed4f8f1660a1525759e when convenient.

Data as of 26 Oct 2026, 19:44 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in ef6d27af71e1dc43181ec797a6aaa77c27c36786, ed74e8d603df457bfcf16ed4f8f1660a1525759e
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to ef6d27af71e1dc43181ec797a6aaa77c27c36786 or ed74e8d603df457bfcf16ed4f8f1660a1525759e.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8ed8b02396172b137ca8c78c3cb999ddf4fb0bbf, < ef6d27af71e1dc43181ec797a6aaa77c27c36786
Fixed in
  • ef6d27af71e1dc43181ec797a6aaa77c27c36786
LinuxLinuxAffected
  • ≥ 8ed8b02396172b137ca8c78c3cb999ddf4fb0bbf, < ed74e8d603df457bfcf16ed4f8f1660a1525759e
Fixed in
  • ed74e8d603df457bfcf16ed4f8f1660a1525759e
LinuxLinuxAffected
  • =7.1
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: reject a command chain that carries no commands A chain whose command_count is zero passes the payload length check, because struct_size(payload, data, 0) is just the header. The fill loop then does not run, so offset stays zero and the request is submitted with a zero-length buffer. On firmware without AIE2_NPU_COMMAND that ends at the opcode check, since op is still ERT_INVALID_CMD and aie2_get_chain_msg_op() answers MSG_OP_MAX_OPCODE. aie2_get_npu_chain_msg_op() answers MSG_OP_CHAIN_EXEC_NPU whatever it is given, so there the submission continues to drm_clflush_virt_range(cmd_buf, 0), which reads the byte before the buffer and faults on the vmap guard page. EXEC_CMD is reachable by any process that can open the render node. Reject the request instead.

References

Community reviews

Loading reviews…