Look up another CVE · open CVE-2013-7445 in the interactive tracker
CVE-2013-7445
The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows cont…
The kernel CNA record carries no publication date. Subsystem unknown. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2013-7445 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | won't fix | 6.1.190-1 | Debian has decided against an update for bookworm: Minor issue, requires invasive changes. Moving to a newer release is the way to get the fix. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | vulnerable | 7.2.11-1 | No fix published anywhere yet, neither in Debian nor upstream for the series forky tracks. Watch the Debian tracker page for this CVE. |
| Debian unstablesid | vulnerable | 7.2.11-1 | No fix published anywhere yet, neither in Debian nor upstream for the series sid tracks. Watch the Debian tracker page for this CVE. |
The vulnerability
What the bug is
The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated by JavaScript code that creates many CANVAS elements for rendering by Chrome or Firefox.
Where it lives
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.
Signals
- Published
- unknown
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 2.76%, higher than 86.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- unknown
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2013-7445, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.