NVD / CVE Program· CNA Linux

CVE-2026-45914: Revert "hwmon: (ibmpex) fix use-after-free in high/low store"

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 05112ba67c824ab416cd54307c0b50aba9f0047a, 14a38784e09aebc21207dc32fffa05247fc3dd64, 5.10.252.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 05112ba67c824ab416cd54307c0b50aba9f0047a, 14a38784e09aebc21207dc32fffa05247fc3dd64, 5.10.252 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: Revert "hwmon: (ibmpex) fix use-after-free in high/low store" This reverts commit 6946c726c3f4c36f0f049e6f97e88c510b15f65d. Jean Delvare points out that the patch does not completely fix the reported problem, that it in fact introduces a (new) race condition, and that it may actually not be needed in the first place. Various AI reviews agree. Specific and relevant AI feedback: " This reordering sets the driver data to NULL before removing the sensor attributes in the loop below. ibmpex_show_sensor() retrieves this driver data via dev_get_drvdata() but does not check if it is NULL before dereferencing it to access data->sensors[]. If a userspace process reads a sensor file (like temp1_input) while this delete function is running, could it race with the dev_set_drvdata(..., NULL) call here and crash in ibmpex_show_sensor()? Would it be safer to keep the original order where device_remove_file() is called before clearing the driver data? device_remove_file() should wait for any active sysfs callbacks to complete, which might already prevent the use-after-free this patch intends to fix. " Revert the offending patch. If it can be shown that the originally reported alleged race condition does indeed exist, it can always be re-introduced with a complete fix.

HighCVSS 7.8 · v3.1—No exploit Fix available

BDU:2026-11775

Published: May 27, 2026
Updated: Jun 24, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.10.248 and later · before 5.10.252
linux linux kernel6.1.160 and later · before 6.1.165
linux linux kernel6.6.120 and later · before 6.6.128
linux linux kernel6.12.64 and later · before 6.12.75
linux linux kernel6.18.3 and later · before 6.18.14
linux linux kernel6.19.1 and later · before 6.19.4
linux linux kernel6.19

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 6.19affected
- 3ce9b7ae9d4d148672b35147aaf7987a4f82bb94 and later · before 05112ba67c824ab416cd54307c0b50aba9f0047aaffected · git
- 533ead425f8109b02fecc7e72d612b8898ec347a and later · before efd68429f23fb4015b0ebc2392334059e06fad18affected · git
- fa37adcf1d564ef58b9dfb01b6c36d35c5294bad and later · before f448acd86835a650f9ea83460b9ca347d3aafba5affected · git
- 68d62e5bebbd118b763e8bb210d5cf2198ef450c and later · before 914b47c9b824d3d74f31c764163edf93302100b1affected · git
- 5aa2139201667c1f644601e4529c4acd6bf8db5a and later · before 14a38784e09aebc21207dc32fffa05247fc3dd64affected · git
- 6946c726c3f4c36f0f049e6f97e88c510b15f65d and later · before 894d9c7aab68fd0c70c78b1d03c8fa589fb0f67daffected · git
- 6946c726c3f4c36f0f049e6f97e88c510b15f65d and later · before 8bde3e395a85017f12af2b0ba5c3684f5af9c006affected · git
- 5.10.248 and later · before 5.10.252affected · semver
- 6.1.160 and later · before 6.1.165affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.170-1	6.1.170-1
Debian:13	linux	before 6.12.85-1	6.12.85-1
Debian:14	linux	before 6.18.14-1	6.18.14-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-45909May 27, 2026 · clk: mediatek: Drop __initconst from gates
31Monitor
← EarlierCVE-2026-45911May 27, 2026 · usb: cdns3: fix role switching during resume
22Monitor
Later →CVE-2026-45916May 27, 2026 · power: supply: sbs-battery: Fix use-after-free in power_supply_changed()
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	05112ba67c824ab416cd54307c0b50aba9f0047a	Vendor (CNA)
Linux Linux	14a38784e09aebc21207dc32fffa05247fc3dd64	Vendor (CNA)
Linux Linux	5.10.252	Vendor (CNA)
Linux Linux	6.1.165	Vendor (CNA)
Linux Linux	6.12.75	Vendor (CNA)
Linux Linux	6.18.14	Vendor (CNA)
Linux Linux	6.6.128	Vendor (CNA)
Linux Linux	894d9c7aab68fd0c70c78b1d03c8fa589fb0f67d	Vendor (CNA)
Linux Linux	8bde3e395a85017f12af2b0ba5c3684f5af9c006	Vendor (CNA)
Linux Linux	914b47c9b824d3d74f31c764163edf93302100b1	Vendor (CNA)
Linux Linux	efd68429f23fb4015b0ebc2392334059e06fad18	Vendor (CNA)
Linux Linux	f448acd86835a650f9ea83460b9ca347d3aafba5	Vendor (CNA)
debian:linux	6.1.170-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/05112ba67c824ab416cd54307c0b50aba9f0047a

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records