device property: initialize the remaining fields of fwnode_handle in fwnode_init()
Noroxi assessment
Priority: Monitor (action score 31/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).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0198d579948322cda5178b9672d448375a32f947, 173b61c9276c7b3a5fbcc63ae7aafc897fee1e18, 7eba000621fff223dd7bab484d48918c7c77a307.
Low priority for now. Upgrade to Linux Linux 0198d579948322cda5178b9672d448375a32f947, 173b61c9276c7b3a5fbcc63ae7aafc897fee1e18, 7eba000621fff223dd7bab484d48918c7c77a307 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: device property: initialize the remaining fields of fwnode_handle in fwnode_init() If a firmware node is allocated on the stack (for instance: temporary software node whose life-time we control) or on the heap - but using a non-zeroing allocation function - and initialized using fwnode_init(), its secondary pointer will contain uninitialized memory which likely will be neither NULL nor IS_ERR() and so may end up being dereferenced (for example: in dev_to_swnode()). Set fwnode->secondary to NULL on initialization. While at it: initialize the remaining fields of struct fwnode_handle too just to be sure. [ Fix typo in commit message. - Danilo ]
- Published
- Aug 15, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-665
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 5.11affected
- 01bb86b380a306bd937c96da36f66429f3362137 and later · before 0198d579948322cda5178b9672d448375a32f947affected · git
- 01bb86b380a306bd937c96da36f66429f3362137 and later · before 173b61c9276c7b3a5fbcc63ae7aafc897fee1e18affected · git
- 01bb86b380a306bd937c96da36f66429f3362137 and later · before f0b4e1cc8ad76baf49d898727eb52e91a4ef0544affected · git
- 01bb86b380a306bd937c96da36f66429f3362137 and later · before c8542b68ba6ef4f61072098893a3f5b71c569b6caffected · git
- 01bb86b380a306bd937c96da36f66429f3362137 and later · before 9c86a1f930bb2ddb85f867b4736716e82a4a4683affected · git
- 01bb86b380a306bd937c96da36f66429f3362137 and later · before c81e2af41de6a159837c7129a4fc444ac6e48046affected · git
- 01bb86b380a306bd937c96da36f66429f3362137 and later · before 7eba000621fff223dd7bab484d48918c7c77a307affected · git
- before 5.11not affected · semver
- 5.15.212 and later · up to and including 5.15.*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 | 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.5-1 | 7.1.5-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-74437Aug 15, 2026 · media: uvcvideo: Fix deadlock if uvc_status_stop is called from async_ctrl.work0Monitor
- ← EarlierCVE-2026-74438Aug 15, 2026 · crypto: sun4i-ss - Remove insecure and unused rng_alg31Monitor
- Later →CVE-2026-68470Aug 15, 2026 · wifi: mac80211: validate extension-frame layout before RX35Monitor
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 | 0198d579948322cda5178b9672d448375a32f947 | Vendor (CNA) |
| Linux Linux | 173b61c9276c7b3a5fbcc63ae7aafc897fee1e18 | Vendor (CNA) |
| Linux Linux | 7eba000621fff223dd7bab484d48918c7c77a307 | Vendor (CNA) |
| Linux Linux | 9c86a1f930bb2ddb85f867b4736716e82a4a4683 | Vendor (CNA) |
| Linux Linux | c81e2af41de6a159837c7129a4fc444ac6e48046 | Vendor (CNA) |
| Linux Linux | c8542b68ba6ef4f61072098893a3f5b71c569b6c | Vendor (CNA) |
| Linux Linux | f0b4e1cc8ad76baf49d898727eb52e91a4ef0544 | Vendor (CNA) |
| 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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-665 · Improper InitializationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/173b61c9276c7b3a5fbcc63ae7aafc897fee1e18
- git.kernel.org/stable/c/7eba000621fff223dd7bab484d48918c7c77a307
- git.kernel.org/stable/c/9c86a1f930bb2ddb85f867b4736716e82a4a4683
- git.kernel.org/stable/c/c81e2af41de6a159837c7129a4fc444ac6e48046
- git.kernel.org/stable/c/c8542b68ba6ef4f61072098893a3f5b71c569b6c
- git.kernel.org/stable/c/f0b4e1cc8ad76baf49d898727eb52e91a4ef0544
Vendor advisories and official records. Exploit/PoC links are deliberately left out.