CVE-2026-74391: tracing: Bound synthetic-field strings with seq_buf
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 0c584c27f6649a93ec12061cc779a4bd8f7c1434, 88b901fdc1662b131ff908cbd017333b61e7acc8, 9f8ef2e1e95a42044e614b0a5277e3f53f545135.
Low priority for now. Upgrade to Linux Linux 0c584c27f6649a93ec12061cc779a4bd8f7c1434, 88b901fdc1662b131ff908cbd017333b61e7acc8, 9f8ef2e1e95a42044e614b0a5277e3f53f545135 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: tracing: Bound synthetic-field strings with seq_buf The synthetic field helpers build a prefixed synthetic variable name and a generated hist command in fixed MAX_FILTER_STR_VAL buffers. The current code appends those strings with raw strcat(), so long key lists, field names, or saved filters can run past the end of the staging buffers. Build both strings with seq_buf and propagate -E2BIG if either the synthetic variable name or the generated command exceeds MAX_FILTER_STR_VAL. This keeps the existing tracing-side limit while using the helper intended for bounded command construction. [ sdr: Moved struct seq_buf *s for upside-down x-mas tree formatting ]
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th 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.
Is your version affected? Check itNoroxi 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.17affected
- 02205a6752f223779a1b0e9e8ffacbea6e717851 and later · before 9f8ef2e1e95a42044e614b0a5277e3f53f545135affected · git
- 02205a6752f223779a1b0e9e8ffacbea6e717851 and later · before 0c584c27f6649a93ec12061cc779a4bd8f7c1434affected · git
- 02205a6752f223779a1b0e9e8ffacbea6e717851 and later · before 88b901fdc1662b131ff908cbd017333b61e7acc8affected · git
- 02205a6752f223779a1b0e9e8ffacbea6e717851 and later · before baa333b2700a7fa3529d504529c8c10060fd687caffected · git
- 02205a6752f223779a1b0e9e8ffacbea6e717851 and later · before cf334620036ad2250e008c7e7bb6646a3938b7b0affected · git
- 02205a6752f223779a1b0e9e8ffacbea6e717851 and later · before f07883450eb14d1cf020b55d9f3a7ec5683bcd26affected · git
- before 4.17not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.145 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.100-1 | 6.12.100-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-74389Aug 15, 2026 · RDMA/hns: Fix log flood after cmd_mbox failure0Monitor
- ← EarlierCVE-2026-74390Aug 15, 2026 · RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs31Monitor
- Later →CVE-2026-74394Aug 15, 2026 · RDMA/srpt: fix integer overflow in immediate data length check39Monitor
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 | 0c584c27f6649a93ec12061cc779a4bd8f7c1434 | Vendor (CNA) |
| Linux Linux | 88b901fdc1662b131ff908cbd017333b61e7acc8 | Vendor (CNA) |
| Linux Linux | 9f8ef2e1e95a42044e614b0a5277e3f53f545135 | Vendor (CNA) |
| Linux Linux | baa333b2700a7fa3529d504529c8c10060fd687c | Vendor (CNA) |
| Linux Linux | cf334620036ad2250e008c7e7bb6646a3938b7b0 | Vendor (CNA) |
| Linux Linux | f07883450eb14d1cf020b55d9f3a7ec5683bcd26 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | 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/88b901fdc1662b131ff908cbd017333b61e7acc8
- git.kernel.org/stable/c/9f8ef2e1e95a42044e614b0a5277e3f53f545135
- git.kernel.org/stable/c/baa333b2700a7fa3529d504529c8c10060fd687c
- git.kernel.org/stable/c/cf334620036ad2250e008c7e7bb6646a3938b7b0
- git.kernel.org/stable/c/f07883450eb14d1cf020b55d9f3a7ec5683bcd26
Vendor advisories and official records. Exploit/PoC links are deliberately left out.