audit: fix possible soft lockup in __audit_inode_child()
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.28% (FIRST EPSS).
- Fixed version: Linux Linux 0152e7758cc4e9f8bfba8dbea4438d8e488d6c08, 1640c7bd4eddec6c72f3a99cbb74e333a2ce9f5d, 8a40b491372966ba5426e138a53460985565d5a6.
Low priority for now. Upgrade to Linux Linux 0152e7758cc4e9f8bfba8dbea4438d8e488d6c08, 1640c7bd4eddec6c72f3a99cbb74e333a2ce9f5d, 8a40b491372966ba5426e138a53460985565d5a6 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: audit: fix possible soft lockup in __audit_inode_child() Tracefs or debugfs maybe cause hundreds to thousands of PATH records, too many PATH records maybe cause soft lockup. For example: 1. CONFIG_KASAN=y && CONFIG_PREEMPTION=n 2. auditctl -a exit,always -S open -k key 3. sysctl -w kernel.watchdog_thresh=5 4. mkdir /sys/kernel/debug/tracing/instances/test There may be a soft lockup as follows: watchdog: BUG: soft lockup - CPU#45 stuck for 7s! [mkdir:15498] Kernel panic - not syncing: softlockup: hung tasks Call trace: dump_backtrace+0x0/0x30c show_stack+0x20/0x30 dump_stack+0x11c/0x174 panic+0x27c/0x494 watchdog_timer_fn+0x2bc/0x390 __run_hrtimer+0x148/0x4fc __hrtimer_run_queues+0x154/0x210 hrtimer_interrupt+0x2c4/0x760 arch_timer_handler_phys+0x48/0x60 handle_percpu_devid_irq+0xe0/0x340 __handle_domain_irq+0xbc/0x130 gic_handle_irq+0x78/0x460 el1_irq+0xb8/0x140 __audit_inode_child+0x240/0x7bc tracefs_create_file+0x1b8/0x2a0 trace_create_file+0x18/0x50 event_create_dir+0x204/0x30c __trace_add_new_event+0xac/0x100 event_trace_add_tracer+0xa0/0x130 trace_array_create_dir+0x60/0x140 trace_array_create+0x1e0/0x370 instance_mkdir+0x90/0xd0 tracefs_syscall_mkdir+0x68/0xa0 vfs_mkdir+0x21c/0x34c do_mkdirat+0x1b4/0x1d4 __arm64_sys_mkdirat+0x4c/0x60 el0_svc_common.constprop.0+0xa8/0x240 do_el0_svc+0x8c/0xc0 el0_svc+0x20/0x30 el0_sync_handler+0xb0/0xb4 el0_sync+0x160/0x180 Therefore, we add cond_resched() to __audit_inode_child() to fix it.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th 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.2%
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
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before d061e2bfc20f2914656385816e0d20566213c54caffected · git
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before 1640c7bd4eddec6c72f3a99cbb74e333a2ce9f5daffected · git
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before f6364fa751d7486502c777f124a14d4d543fc5ebaffected · git
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before 98ef243d5900d75a64539a2165745bffbb155d43affected · git
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before 0152e7758cc4e9f8bfba8dbea4438d8e488d6c08affected · git
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before 9ca08adb75fb40a8f742c371927ee73f9dc753bfaffected · git
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before 8a40b491372966ba5426e138a53460985565d5a6affected · git
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before 8e76b944a7b9bddef190ffe2e29c9ae342ab91edaffected · git
- 5195d8e217a78697152d64fc09a16e063a022465 and later · before b59bc6e37237e37eadf50cd5de369e913f524463affected · git
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.55-1 | 6.1.55-1 |
| Debian:13 | linux | before 6.5.3-1 | 6.5.3-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-2022-50783Dec 24, 2025 · mptcp: use proper req destructor for IPv60Monitor
- ← EarlierCVE-2023-54044Dec 24, 2025 · spmi: Add a check for remove callback when removing a SPMI driver0Monitor
- Later →CVE-2023-54047Dec 24, 2025 · drm/rockchip: dw_hdmi: cleanup drm encoder during unbind0Monitor
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 | 0152e7758cc4e9f8bfba8dbea4438d8e488d6c08 | Vendor (CNA) |
| Linux Linux | 1640c7bd4eddec6c72f3a99cbb74e333a2ce9f5d | Vendor (CNA) |
| Linux Linux | 8a40b491372966ba5426e138a53460985565d5a6 | Vendor (CNA) |
| Linux Linux | 8e76b944a7b9bddef190ffe2e29c9ae342ab91ed | Vendor (CNA) |
| Linux Linux | 98ef243d5900d75a64539a2165745bffbb155d43 | Vendor (CNA) |
| Linux Linux | 9ca08adb75fb40a8f742c371927ee73f9dc753bf | Vendor (CNA) |
| Linux Linux | b59bc6e37237e37eadf50cd5de369e913f524463 | Vendor (CNA) |
| Linux Linux | d061e2bfc20f2914656385816e0d20566213c54c | Vendor (CNA) |
| Linux Linux | f6364fa751d7486502c777f124a14d4d543fc5eb | Vendor (CNA) |
| debian:linux | 6.1.55-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).
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 (8 more)Show less
- git.kernel.org/stable/c/1640c7bd4eddec6c72f3a99cbb74e333a2ce9f5d
- git.kernel.org/stable/c/8a40b491372966ba5426e138a53460985565d5a6
- git.kernel.org/stable/c/8e76b944a7b9bddef190ffe2e29c9ae342ab91ed
- git.kernel.org/stable/c/98ef243d5900d75a64539a2165745bffbb155d43
- git.kernel.org/stable/c/9ca08adb75fb40a8f742c371927ee73f9dc753bf
- git.kernel.org/stable/c/b59bc6e37237e37eadf50cd5de369e913f524463
- git.kernel.org/stable/c/d061e2bfc20f2914656385816e0d20566213c54c
- git.kernel.org/stable/c/f6364fa751d7486502c777f124a14d4d543fc5eb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.