Skip to main content

Linux Kernel EUVDEUVD-2026-55441

| CVE-2026-68340 HIGH
2026-08-10 Linux GHSA-jq56-qr42-62xw
7.7
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.7 HIGH
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
vuln.today AI
5.7 MEDIUM

Injecting malformed OCC responses requires BMC or firmware-level access, warranting PR:H and AC:H; no integrity impact path exists.

3.1 AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:H
4.0 AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 03:06 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.7 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 12:03 cve.org
HIGH 7.7
CVE Published
Aug 10, 2026 - 12:03 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

hwmon: occ: validate poll response sensor blocks

The OCC poll response parser walks a counted list of sensor data blocks. It used the static backing-array capacity as the parse boundary, but a transport response makes only data_length bytes current and valid. A truncated response can therefore make the parser consume a block header or block extent outside the current response.

Use data_length as the parent boundary, prove the fixed poll header and each current block header before reading them, and prove the complete block before advancing. Keep parsed sensor metadata local until the complete response has passed validation, then publish it. Propagate malformed-response errors before publishing the OCC as active.

AnalysisAI

Out-of-bounds read in the Linux kernel hwmon OCC (On-Chip Controller) driver exposes adjacent kernel memory and risks system availability on IBM POWER hardware running affected kernel versions. The poll response parser uses a static backing-array capacity as its parse boundary rather than the data_length field embedded in the firmware response, allowing a truncated OCC reply to cause the parser to read block headers or extents outside the valid response window. Vendor-released patches are available across multiple stable branches; no public exploit or CISA KEV listing exists at the time of analysis.

Technical ContextAI

The On-Chip Controller (OCC) is management firmware embedded in IBM POWER processors, responsible for power and thermal telemetry. The Linux kernel interfaces with it through a polling driver in drivers/hwmon/occ/, which walks a counted list of sensor data blocks in the firmware's poll response. The vulnerable code used the static backing-array size as the parse loop boundary rather than the data_length value embedded in the response header. This is a classic unchecked-length over-read: if the firmware sends a truncated reply - whether due to firmware bugs, transport corruption, or a malicious BMC - the parser advances beyond the valid response buffer, reading block headers or extents from uninitialized or adjacent kernel memory. The fix, applied across five stable-tree backport commits, adds explicit data_length boundary proofs before reading any block header or extent, defers publishing parsed sensor metadata until the full response passes validation, and propagates malformed-response errors before marking the OCC active. While no CWE was formally assigned, CWE-125 (Out-of-bounds Read) and CWE-20 (Improper Input Validation) are the applicable root-cause classes. Affected CPE: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*.

RemediationAI

The primary remediation is upgrading the Linux kernel to a patched release: 6.6.148, 6.12.101, 6.18.42, 7.1.6, or 7.2-rc5 depending on the stable branch in use. Upstream stable commits are available at https://git.kernel.org/stable/c/b042e538e98b939fccfffc464e2c34c29f0e96ef, https://git.kernel.org/stable/c/538d862cc0dbd5c732fe26d5aad98eae039e6676, https://git.kernel.org/stable/c/112525534ab5cff482d35897ca4ca11fd3a76f46, https://git.kernel.org/stable/c/54cb78eceb4e286ccd5a5c01a4632157860d47f0, and https://git.kernel.org/stable/c/70e76e700fc6c46afb4e17aec099a1ea089b4a22. Where an immediate kernel update is operationally infeasible, the specific compensating control is to blacklist or unload the occ hwmon kernel module (modprobe -r occ; echo 'blacklist occ' >> /etc/modprobe.d/occ.conf) - this disables the entire vulnerable code path with no functional impact beyond losing OCC thermal and power sensor visibility in hwmon. On systems where OCC monitoring is critical to power-capping or thermal management policy, the loss of sensor data may trigger conservative governor behavior; kernel patching should be prioritized in those environments.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

EUVD-2026-55441 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy