---
title: "CVE-2026-81007: Linux Kernel - Buffer Validation Vulnerability"
description: "Linux kernel contains a buffer validation vulnerability in ipmb_write() caused by reading message fields before validating length, letting attackers cause memory corruption or information disclosure, exploit requires crafted IPMB messages."
url: https://panop.io/threat-heartbeat/CVE-2026-81007/
---

# CVE-2026-81007 Linux Kernel - Buffer Validation Vulnerability

Linux kernel contains a buffer validation vulnerability in ipmb\_write() caused by reading message fields before validating length, letting attackers cause memory corruption or information disclosure, exploit requires crafted IPMB messages.

CVSS base score 7.1 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.13% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-81007)

## Details

Type

Buffer Validation Vulnerability

Impact

Information Disclosure, Denial Of Service

CVSS vector

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

Published

11 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix for ipmb\_write validation.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-81007](https://nvd.nist.gov/vuln/detail/CVE-2026-81007)
- [https://git.kernel.org/stable/c/7d66d54b974cff0a959e188af844d2d110422767](https://git.kernel.org/stable/c/7d66d54b974cff0a959e188af844d2d110422767)
- [https://git.kernel.org/stable/c/8990c7f6bfc1e7689b7012a7d4d0efb9f07a9c89](https://git.kernel.org/stable/c/8990c7f6bfc1e7689b7012a7d4d0efb9f07a9c89)
- [https://git.kernel.org/stable/c/94f8d20153e348c79bc14dc25f873470518892da](https://git.kernel.org/stable/c/94f8d20153e348c79bc14dc25f873470518892da)
- [https://git.kernel.org/stable/c/e527cd4e80066e1ed070fdc7c705bde340cdcc62](https://git.kernel.org/stable/c/e527cd4e80066e1ed070fdc7c705bde340cdcc62)
- [https://git.kernel.org/stable/c/53637506884dbd5c91a89b1a3547d99d80f8ed2c](https://git.kernel.org/stable/c/53637506884dbd5c91a89b1a3547d99d80f8ed2c)
- [https://git.kernel.org/stable/c/5719431ca2b5fa26560bb38f6202f8b97fa3bbb0](https://git.kernel.org/stable/c/5719431ca2b5fa26560bb38f6202f8b97fa3bbb0)
- [https://git.kernel.org/stable/c/60939bcda6f3f104ef456fdbf3cc5733c0720fb1](https://git.kernel.org/stable/c/60939bcda6f3f104ef456fdbf3cc5733c0720fb1)
- [https://git.kernel.org/stable/c/a84c6e3d188f2c6e674910929eb790634299d6d5](https://git.kernel.org/stable/c/a84c6e3d188f2c6e674910929eb790634299d6d5)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)