CVE-2026-90208: clocksource/drivers/samsung_pwm: Switch to raw_spinlock_t type
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 3b212f9d70805d91febae01d618868f4860e267c, 5720fe5cabda19f395d194ca57321c7b85f8af80, 7eb5764d25c4ac7f5d126621660f7219b61fd2fd; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 3b212f9d70805d91febae01d618868f4860e267c, 5720fe5cabda19f395d194ca57321c7b85f8af80, 7eb5764d25c4ac7f5d126621660f7219b61fd2fd; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: clocksource/drivers/samsung_pwm: Switch to raw_spinlock_t type Samsung PWM timer might be used as a clock source on some legacy systems. When PREEMPT_RT is enabled on ARM, regular spinlock is converted to a sleeping lock (mutex-based), which must not be used in atomic context such as hard interrupt handlers. Switch the samsung_pwm_lock to the raw_spinlock, which remains a true non-sleeping spinlock even under PREEMPT_RT.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th 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.10affected
- f11899894c0a683c754ca71b45f7c9c3d35a3a1c and later · before 9c97311a5f5d388eece66fc415167b38f35fe6a1affected · git
- f11899894c0a683c754ca71b45f7c9c3d35a3a1c and later · before 8f823b47eb889ea70f4c360164e96453f40e3646affected · git
- f11899894c0a683c754ca71b45f7c9c3d35a3a1c and later · before 5720fe5cabda19f395d194ca57321c7b85f8af80affected · git
- f11899894c0a683c754ca71b45f7c9c3d35a3a1c and later · before a25ea67a913f98b8461aff1e9e3a5f6dc2378395affected · git
- f11899894c0a683c754ca71b45f7c9c3d35a3a1c and later · before 7eb5764d25c4ac7f5d126621660f7219b61fd2fdaffected · git
- f11899894c0a683c754ca71b45f7c9c3d35a3a1c and later · before 3b212f9d70805d91febae01d618868f4860e267caffected · git
- before 3.10not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not 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 | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-90206Sep 17, 2026 · nvmet: fix max_qid race between configfs and controller allocation0Monitor
- ← EarlierCVE-2026-90207Sep 17, 2026 · ALSA: seq: midi: Serialize input teardown with event_input31Monitor
- Later →CVE-2026-90209Sep 17, 2026 · s390/debug: Fix deadlock during unregister0Monitor
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 | 3b212f9d70805d91febae01d618868f4860e267c | Vendor (CNA) |
| Linux Linux | 5720fe5cabda19f395d194ca57321c7b85f8af80 | Vendor (CNA) |
| Linux Linux | 7eb5764d25c4ac7f5d126621660f7219b61fd2fd | Vendor (CNA) |
| Linux Linux | 8f823b47eb889ea70f4c360164e96453f40e3646 | Vendor (CNA) |
| Linux Linux | 9c97311a5f5d388eece66fc415167b38f35fe6a1 | Vendor (CNA) |
| Linux Linux | a25ea67a913f98b8461aff1e9e3a5f6dc2378395 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | 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 (5 more)Show less
- git.kernel.org/stable/c/5720fe5cabda19f395d194ca57321c7b85f8af80
- git.kernel.org/stable/c/7eb5764d25c4ac7f5d126621660f7219b61fd2fd
- git.kernel.org/stable/c/8f823b47eb889ea70f4c360164e96453f40e3646
- git.kernel.org/stable/c/9c97311a5f5d388eece66fc415167b38f35fe6a1
- git.kernel.org/stable/c/a25ea67a913f98b8461aff1e9e3a5f6dc2378395
Vendor advisories and official records. Exploit/PoC links are deliberately left out.