Look up another CVE · open CVE-2023-4134 in the interactive tracker
CVE-2023-4134
A use-after-free vulnerability was found in the cyttsp4_core driver in the Linux kernel
The kernel CNA record carries no publication date. Subsystem unknown. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2023-4134 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 | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.4.4-1 | Update the kernel and reboot. Fixed in 6.4.4-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.4.4-1 | Update the kernel and reboot. Fixed in 6.4.4-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.4.4-1 | Update the kernel and reboot. Fixed in 6.4.4-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
A use-after-free vulnerability was found in the cyttsp4_core driver in the Linux kernel. This issue occurs in the device cleanup routine due to a possible rearming of the watchdog_timer from the workqueue. This could allow a local user to crash the system, causing a denial of service.
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
- 0.20%, higher than 9.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- unknown
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2023-4134, 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.