drm/bridge: tc358767: clamp the reported AUX read size to the request
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 33c0b072e31dee98a754d9bd01800359dfeb9e8f, 424b762cc26d512e3e7421e57e41b4b55be2400b, 57c567e0e8aa76f6e3e8f39d7f40c20bc37e76af; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 33c0b072e31dee98a754d9bd01800359dfeb9e8f, 424b762cc26d512e3e7421e57e41b4b55be2400b, 57c567e0e8aa76f6e3e8f39d7f40c20bc37e76af; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.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: drm/bridge: tc358767: clamp the reported AUX read size to the request tc_aux_transfer() clamps an AUX read to the payload limit: size_t size = min_t(size_t, DP_AUX_MAX_PAYLOAD_BYTES - 1, msg->size); After the transfer it replaces size with the byte count the controller reports in AUX_BYTES: if (size) size = FIELD_GET(AUX_BYTES, auxstatus); AUX_BYTES is GENMASK(15, 8), so it can be up to 255. Nothing clamps it back to the request. tc_aux_read_data() reads that many bytes into the 16-byte auxrdata stack buffer, then copies them into the caller buffer. A reported count of 255 makes the read run to 256 bytes and overruns both. The controller should never report more than it was asked to transfer, so this is defense in depth rather than a live hole. The reported count is only lightly trusted, and the check is cheap. Clamp it back to the request, the same way ti-sn65dsi86 does in commit aca58eac52b8 ("drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer").
- Published
- Sep 17, 2026
- Updated
- Sep 17, 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.
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.4affected
- 12dfe7c4d9c53442efcb4113cff505f60d654906 and later · before ebf00c51c9ac9188e2806a2b842418805ee879beaffected · git
- 12dfe7c4d9c53442efcb4113cff505f60d654906 and later · before 424b762cc26d512e3e7421e57e41b4b55be2400baffected · git
- 12dfe7c4d9c53442efcb4113cff505f60d654906 and later · before dd6274706bec30d005bff0587a4262d01dc2775aaffected · git
- 12dfe7c4d9c53442efcb4113cff505f60d654906 and later · before 982caa744fce79d18f2920382aaeb0da821a6e73affected · git
- 12dfe7c4d9c53442efcb4113cff505f60d654906 and later · before 33c0b072e31dee98a754d9bd01800359dfeb9e8faffected · git
- 12dfe7c4d9c53442efcb4113cff505f60d654906 and later · before 57c567e0e8aa76f6e3e8f39d7f40c20bc37e76afaffected · git
- 12dfe7c4d9c53442efcb4113cff505f60d654906 and later · before 9ff718df547372d70ca20ad8e66a3fb1300936b2affected · git
- 12dfe7c4d9c53442efcb4113cff505f60d654906 and later · before ec6444a00c49e6c2b5e9a507272a28126677f9eeaffected · git
- before 5.4not 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.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| 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-93065Sep 17, 2026 · wifi: iwlwifi: fix counter type in iwl_fwrt_dump_error_logs0Monitor
- ← EarlierCVE-2026-93066Sep 17, 2026 · x86/mm/pat: Take cpa_lock around large-page collapse0Monitor
- Later →CVE-2026-93068Sep 17, 2026 · drm/amd/display: Fix DM I2C teardown race0Monitor
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 | 33c0b072e31dee98a754d9bd01800359dfeb9e8f | Vendor (CNA) |
| Linux Linux | 424b762cc26d512e3e7421e57e41b4b55be2400b | Vendor (CNA) |
| Linux Linux | 57c567e0e8aa76f6e3e8f39d7f40c20bc37e76af | Vendor (CNA) |
| Linux Linux | 982caa744fce79d18f2920382aaeb0da821a6e73 | Vendor (CNA) |
| Linux Linux | 9ff718df547372d70ca20ad8e66a3fb1300936b2 | Vendor (CNA) |
| Linux Linux | dd6274706bec30d005bff0587a4262d01dc2775a | Vendor (CNA) |
| Linux Linux | ebf00c51c9ac9188e2806a2b842418805ee879be | Vendor (CNA) |
| Linux Linux | ec6444a00c49e6c2b5e9a507272a28126677f9ee | 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 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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.
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 (7 more)Show less
- git.kernel.org/stable/c/424b762cc26d512e3e7421e57e41b4b55be2400b
- git.kernel.org/stable/c/57c567e0e8aa76f6e3e8f39d7f40c20bc37e76af
- git.kernel.org/stable/c/982caa744fce79d18f2920382aaeb0da821a6e73
- git.kernel.org/stable/c/9ff718df547372d70ca20ad8e66a3fb1300936b2
- git.kernel.org/stable/c/dd6274706bec30d005bff0587a4262d01dc2775a
- git.kernel.org/stable/c/ebf00c51c9ac9188e2806a2b842418805ee879be
- git.kernel.org/stable/c/ec6444a00c49e6c2b5e9a507272a28126677f9ee
Vendor advisories and official records. Exploit/PoC links are deliberately left out.