CVE-2026-98537: workqueue: Fix NULL current_pwq deref in flush dependency check
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.22% (FIRST EPSS).
- Fixed version: Linux Linux 0c6b9b1e295aeff1132ac7aa738148cc65f06485, 1dccf5dc2f8fe688270b261ca4216e03c6a1e674, 513121e69388604619ea8c0ee07e86a3d1b5b5dc; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0c6b9b1e295aeff1132ac7aa738148cc65f06485, 1dccf5dc2f8fe688270b261ca4216e03c6a1e674, 513121e69388604619ea8c0ee07e86a3d1b5b5dc; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.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: workqueue: Fix NULL current_pwq deref in flush dependency check check_flush_dependency() uses current_wq_worker() to determine whether the caller is a workqueue worker and then dereferences worker->current_pwq to test whether the current workqueue is WQ_MEM_RECLAIM. current_wq_worker() only means that %current has PF_WQ_WORKER set. A kworker can reach check_flush_dependency() while it is not executing a work item. One such path is worker_thread() acting as the pool manager, where create_worker() does GFP_KERNEL allocation and the allocation path invokes the OOM notifier. In that state worker->current_pwq is NULL because current_pwq is set only by process_one_work() and cleared again after the work function returns. [ 416.760634][ T375] Call trace: [ 416.760638][ T375] check_flush_dependency+0x80/0x120 (P) [ 416.760648][ T375] __flush_work+0x98/0x224 [ 416.760657][ T375] flush_work+0x30/0x44 [ 416.760665][ T375] ... [ 416.760710][ T375] blocking_notifier_call_chain+0x58/0xa0 [ 416.760719][ T375] out_of_memory+0xb4/0x458 [ 416.760730][ T375] __alloc_pages_may_oom+0x11c/0x1a8 [ 416.760739][ T375] __alloc_pages_slowpath+0x314/0x46c [ 416.760746][ T375] __alloc_frozen_pages_noprof+0x110/0x1a4 [ 416.760753][ T375] new_slab+0x12c/0x484 [ 416.760759][ T375] ___slab_alloc+0x7a8/0xc7c [ 416.760765][ T375] __slab_alloc+0x74/0xd8 [ 416.760772][ T375] __kmalloc_cache_node_noprof+0x2ac/0x304 [ 416.760779][ T375] alloc_worker+0x28/0x60 [ 416.760785][ T375] create_worker+0x4c/0x20c [ 416.760790][ T375] worker_thread+0xe8/0x2b8 [ 416.760796][ T375] kthread+0x1a8/0x200 [ 416.760805][ T375] ret_from_fork+0x10/0x20 Guard the WQ_MEM_RECLAIM-worker warning with worker->current_pwq. If the kworker is not currently executing a work item, there is no current workqueue to diagnose with that warning. The PF_MEMALLOC warning is left unchanged so explicit reclaim context flushing a !WQ_MEM_RECLAIM target is still reported.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th 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
- 4.5affected
- fca839c00a12d682cb59b3b620d109a1d850b262 and later · before 8ffececcb88262389b4f91fed0fe4884b68204bcaffected · git
- fca839c00a12d682cb59b3b620d109a1d850b262 and later · before 9bb739a5c5a570c28a62afb98e9326e2a49743c1affected · git
- fca839c00a12d682cb59b3b620d109a1d850b262 and later · before cc190a6a1d20b87e6a9435202fc2a3bd84c79fb3affected · git
- fca839c00a12d682cb59b3b620d109a1d850b262 and later · before 513121e69388604619ea8c0ee07e86a3d1b5b5dcaffected · git
- fca839c00a12d682cb59b3b620d109a1d850b262 and later · before 0c6b9b1e295aeff1132ac7aa738148cc65f06485affected · git
- fca839c00a12d682cb59b3b620d109a1d850b262 and later · before 1dccf5dc2f8fe688270b261ca4216e03c6a1e674affected · git
- fca839c00a12d682cb59b3b620d109a1d850b262 and later · before f97e6d0572d1b39998e053732332bc3cfdd0b9aaaffected · git
- fca839c00a12d682cb59b3b620d109a1d850b262 and later · before db6365ced4d5855e321f772b240c0e473bcfcdd5affected · git
- before 4.5not 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-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-98535Oct 18, 2026 · fsl/fman: Fix clk reference leak in read_dts_node()0Monitor
- ← EarlierCVE-2026-98536Oct 18, 2026 · writeback: report a Tasks-RCU quiescent state per cgwb drain pass0Monitor
- Later →CVE-2026-98538Oct 18, 2026 · writeback: bound cleanup_offline_cgwb() rescans by rotating scanned inodes0Monitor
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 | 0c6b9b1e295aeff1132ac7aa738148cc65f06485 | Vendor (CNA) |
| Linux Linux | 1dccf5dc2f8fe688270b261ca4216e03c6a1e674 | Vendor (CNA) |
| Linux Linux | 513121e69388604619ea8c0ee07e86a3d1b5b5dc | Vendor (CNA) |
| Linux Linux | 8ffececcb88262389b4f91fed0fe4884b68204bc | Vendor (CNA) |
| Linux Linux | 9bb739a5c5a570c28a62afb98e9326e2a49743c1 | Vendor (CNA) |
| Linux Linux | cc190a6a1d20b87e6a9435202fc2a3bd84c79fb3 | Vendor (CNA) |
| Linux Linux | db6365ced4d5855e321f772b240c0e473bcfcdd5 | Vendor (CNA) |
| Linux Linux | f97e6d0572d1b39998e053732332bc3cfdd0b9aa | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · 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.
- Published
- Fix recordedsame day
- TodayNov 2, 2026+15 d
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-1351 · Oct 19, 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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1dccf5dc2f8fe688270b261ca4216e03c6a1e674
- git.kernel.org/stable/c/513121e69388604619ea8c0ee07e86a3d1b5b5dc
- git.kernel.org/stable/c/8ffececcb88262389b4f91fed0fe4884b68204bc
- git.kernel.org/stable/c/9bb739a5c5a570c28a62afb98e9326e2a49743c1
- git.kernel.org/stable/c/cc190a6a1d20b87e6a9435202fc2a3bd84c79fb3
- git.kernel.org/stable/c/db6365ced4d5855e321f772b240c0e473bcfcdd5
- git.kernel.org/stable/c/f97e6d0572d1b39998e053732332bc3cfdd0b9aa
Vendor advisories and official records. Exploit/PoC links are deliberately left out.