CVE-2026-68090: debugobjects: Plug race against a concurrent OOM disable
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 1f4f02b336c3be125c8fcf87df73db2e0e028b8b, 203a965bf2ab43130778d8214fb0c3c8c2d19cdf, 23da32e88627e63e0864f59f4c63a2dc0ab851a3; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1f4f02b336c3be125c8fcf87df73db2e0e028b8b, 203a965bf2ab43130778d8214fb0c3c8c2d19cdf, 23da32e88627e63e0864f59f4c63a2dc0ab851a3; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 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: 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
- Aug 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- 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
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 helpAffected 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.
—
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
- 3.3affected
- b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and later · before 2d5e320b7ab9b25229ac4331541964a58b5e1d29affected · git
- b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and later · before 203a965bf2ab43130778d8214fb0c3c8c2d19cdfaffected · git
- b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and later · before 23da32e88627e63e0864f59f4c63a2dc0ab851a3affected · git
- b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and later · before d663fbf28b2eebe665bb9cf828d7d528e5a8707eaffected · git
- b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and later · before e2e255d07723c330dded8e576ce28a8d23a692ceaffected · git
- b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and later · before c00164c9e7fa6145886ad666806cb5347895de5caffected · git
- b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and later · before 1f4f02b336c3be125c8fcf87df73db2e0e028b8baffected · git
- b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 and later · before b81dde13cc163450dcb402dcc915ef13ba241e01affected · git
- before 3.3not affected · 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68088Aug 10, 2026 · usb: gadget: function: rndis: add length check to response query0Monitor
- ← EarlierCVE-2026-68089Aug 10, 2026 · iio: core: fix uninitialized data in debugfs0Monitor
- Later →CVE-2026-68092Aug 10, 2026 · time/jiffies: Register jiffies clocksource before usage0Monitor
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 | 1f4f02b336c3be125c8fcf87df73db2e0e028b8b | Vendor (CNA) |
| Linux Linux | 203a965bf2ab43130778d8214fb0c3c8c2d19cdf | Vendor (CNA) |
| Linux Linux | 23da32e88627e63e0864f59f4c63a2dc0ab851a3 | Vendor (CNA) |
| Linux Linux | 2d5e320b7ab9b25229ac4331541964a58b5e1d29 | Vendor (CNA) |
| Linux Linux | b81dde13cc163450dcb402dcc915ef13ba241e01 | Vendor (CNA) |
| Linux Linux | c00164c9e7fa6145886ad666806cb5347895de5c | Vendor (CNA) |
| Linux Linux | d663fbf28b2eebe665bb9cf828d7d528e5a8707e | Vendor (CNA) |
| Linux Linux | e2e255d07723c330dded8e576ce28a8d23a692ce | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.180-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/203a965bf2ab43130778d8214fb0c3c8c2d19cdf
- git.kernel.org/stable/c/23da32e88627e63e0864f59f4c63a2dc0ab851a3
- git.kernel.org/stable/c/2d5e320b7ab9b25229ac4331541964a58b5e1d29
- git.kernel.org/stable/c/b81dde13cc163450dcb402dcc915ef13ba241e01
- git.kernel.org/stable/c/c00164c9e7fa6145886ad666806cb5347895de5c
- git.kernel.org/stable/c/d663fbf28b2eebe665bb9cf828d7d528e5a8707e
- git.kernel.org/stable/c/e2e255d07723c330dded8e576ce28a8d23a692ce
Vendor advisories and official records. Exploit/PoC links are deliberately left out.