Unknown

CVE-2026-68090 — debugobjects: Plug race against a concurrent OOM disable

In the Linux kernel, the following vulnerability has been resolved: debugobjects: Plug race against a concurrent OOM disable syzbot reported a puzzling splat: WARNING: kernel/time/hrtimer.c:443 at stub_timer+0xa/0x20 stub_timer() is installed as timer callback function in hrtimer_fixup_assert_init(), which is invoked when debug_object_assert_init() can't find a shadow object. In that case debug objects emits a warning about it before invoking the fixup. Though the provided console log lacks this warning and instead has the following a few seconds before the splat: ODEBUG: Out of memory. ODEBUG disabled So the object was looked up in debug_object_assert_init() and the lookup failed due a concurrent out of memory situation which disabled debug objects and freed the shadow objects: debug_object_assert_init() if (!debug_objects_enabled) return; obj = alloc(); if (!obj) { // Out of memory debug_objects_enabled = false; free_objects(); obj = lookup_or_alloc(); // The lookup failed because the other side // removed the objects, so this returns // an error code as the object in question // is not statically initialized if (!IS_ERR_OR_NULL(obj)) return; if (!obj) { debug_oom(); return; } print(...) if (!debug_objects_enabled) return; fixup(...) The debug object splat is skipped because debug_objects_enabled is false, but the fixup callback is invoked unconditionally, which makes the timer disfunctional. This is only a problem in debug_object_assert_init() and debug_object_activate() as both have to handle statically initialized objects and therefore must handle the error pointer return case gracefully. All other places only handle the found/not found case and the NULL pointer return is a signal for OOM. Otherwise they get a valid shadow object. Plug the hole by checking whether debug objects are still enabled before invoking the print and fixup function in those two places.

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

Low

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

EPSS 0.2% (30-day exploitation probability)+1

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

0.18%

ahead of 7% of scored CVEs · Oct 30, 2026

Affects

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.

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

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and < 2d5e320b7ab9b25229ac4331541964a58b5e1d29≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and < 203a965bf2ab43130778d8214fb0c3c8c2d19cdf≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and < 23da32e88627e63e0864f59f4c63a2dc0ab851a3≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and < d663fbf28b2eebe665bb9cf828d7d528e5a8707e≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and < e2e255d07723c330dded8e576ce28a8d23a692ce≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and < c00164c9e7fa6145886ad666806cb5347895de5c≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and < 1f4f02b336c3be125c8fcf87df73db2e0e028b8b≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and < b81dde13cc163450dcb402dcc915ef13ba241e01 and 1 more version 3.3	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.18%

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
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 10, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/2d5e320b7ab9b25229ac4331541964a58b5e1d29
NIST National Vulnerability Database
git.kernel.org/stable/c/1f4f02b336c3be125c8fcf87df73db2e0e028b8b
NIST National Vulnerability Database
git.kernel.org/stable/c/b81dde13cc163450dcb402dcc915ef13ba241e01
NIST National Vulnerability Database
git.kernel.org/stable/c/203a965bf2ab43130778d8214fb0c3c8c2d19cdf
NIST National Vulnerability Database
git.kernel.org/stable/c/d663fbf28b2eebe665bb9cf828d7d528e5a8707e
NIST National Vulnerability Database
git.kernel.org/stable/c/c00164c9e7fa6145886ad666806cb5347895de5c
NIST National Vulnerability Database
git.kernel.org/stable/c/e2e255d07723c330dded8e576ce28a8d23a692ce
NIST National Vulnerability Database
git.kernel.org/stable/c/23da32e88627e63e0864f59f4c63a2dc0ab851a3
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

High CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d

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 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-68090 is "debugobjects: Plug race against a concurrent OOM disable", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. 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.