CVE-2026-80645: rapidio/tsi721: prevent a bad dereference in tsi721_db_dpc()
Noroxi assessment
Priority: Monitor (action score 32/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.40% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 070f356ea4f419e4e85e4089381f4477f41d969e, 13092966ba5d8fb214a4efeddc87f9ed0fd2f945, 3b5c66e922aa6a3331915a14520848a5b3beccc7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 070f356ea4f419e4e85e4089381f4477f41d969e, 13092966ba5d8fb214a4efeddc87f9ed0fd2f945, 3b5c66e922aa6a3331915a14520848a5b3beccc7 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: rapidio/tsi721: prevent a bad dereference in tsi721_db_dpc() With a list_for_each() loop, if we don't find the item we are looking for in the list, then the loop exits with the iterator, which is "dbell" in this loop, pointing to invalid memory. This code uses the "found" variable to determine if we have found the doorbell we are looking for or not. However, the problem that the "found" variable needs to be set to false at the start of each iteration, otherwise after the first correct doorbell, then everything is marked as found. Reset the "found" to false at the start of the iteration and move the variable inside the loop.
- Published
- Aug 28, 2026
- Updated
- Aug 29, 2026
- EPSS
- 0.4% · 34th percentile
- CWE
- —
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.1
- 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
- 3.2affected
- 48618fb4e522d9d02e217ac05f52749545c1af20 and later · before 9e775c3199903d7c09a52530042b1198eab705bdaffected · git
- 48618fb4e522d9d02e217ac05f52749545c1af20 and later · before 81c06ef66c3ab6eeaa72eb790c90ae043cdb3d43affected · git
- 48618fb4e522d9d02e217ac05f52749545c1af20 and later · before 13092966ba5d8fb214a4efeddc87f9ed0fd2f945affected · git
- 48618fb4e522d9d02e217ac05f52749545c1af20 and later · before acd54f42abbbd806464468838dbc04efd203d2beaffected · git
- 48618fb4e522d9d02e217ac05f52749545c1af20 and later · before 3b5c66e922aa6a3331915a14520848a5b3beccc7affected · git
- 48618fb4e522d9d02e217ac05f52749545c1af20 and later · before 070f356ea4f419e4e85e4089381f4477f41d969eaffected · git
- 48618fb4e522d9d02e217ac05f52749545c1af20 and later · before dc28a14f3e4546b2b06098d24177942540581a5faffected · git
- 48618fb4e522d9d02e217ac05f52749545c1af20 and later · before fc15e3a30ddd950f009c76765331783b9af94a87affected · git
- before 3.2not 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.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-80641Aug 28, 2026 · wifi: wlcore: enable the right set of ciphers0Monitor
- ← EarlierCVE-2026-80642Aug 28, 2026 · liveupdate: Reference count incoming FLB data0Monitor
- Later →CVE-2026-80647Aug 28, 2026 · RDMA/hns: Fix warning in poll cq direct mode0Monitor
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 | 070f356ea4f419e4e85e4089381f4477f41d969e | Vendor (CNA) |
| Linux Linux | 13092966ba5d8fb214a4efeddc87f9ed0fd2f945 | Vendor (CNA) |
| Linux Linux | 3b5c66e922aa6a3331915a14520848a5b3beccc7 | Vendor (CNA) |
| Linux Linux | 81c06ef66c3ab6eeaa72eb790c90ae043cdb3d43 | Vendor (CNA) |
| Linux Linux | 9e775c3199903d7c09a52530042b1198eab705bd | Vendor (CNA) |
| Linux Linux | acd54f42abbbd806464468838dbc04efd203d2be | Vendor (CNA) |
| Linux Linux | dc28a14f3e4546b2b06098d24177942540581a5f | Vendor (CNA) |
| Linux Linux | fc15e3a30ddd950f009c76765331783b9af94a87 | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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.
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 (7 more)Show less
- git.kernel.org/stable/c/13092966ba5d8fb214a4efeddc87f9ed0fd2f945
- git.kernel.org/stable/c/3b5c66e922aa6a3331915a14520848a5b3beccc7
- git.kernel.org/stable/c/81c06ef66c3ab6eeaa72eb790c90ae043cdb3d43
- git.kernel.org/stable/c/9e775c3199903d7c09a52530042b1198eab705bd
- git.kernel.org/stable/c/acd54f42abbbd806464468838dbc04efd203d2be
- git.kernel.org/stable/c/dc28a14f3e4546b2b06098d24177942540581a5f
- git.kernel.org/stable/c/fc15e3a30ddd950f009c76765331783b9af94a87
Vendor advisories and official records. Exploit/PoC links are deliberately left out.