CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-72119 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-72119?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-72119?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-72119 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | from 5.10.238 before 5.10.265 |
| Linux | from 5.15.185 before 5.15.216 |
| Linux | from 6.1.141 before 6.1.183 |
| Linux | from 6.6.93 before 6.6.148 |
| Linux | from 6.12.31 before 6.12.101 |
| Linux | from 5.4.294 before 5.5 |
| Linux | from 6.14.9 before 6.15 |
| Linux | 6.15 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 5.10 | 5.10.265 |
| Linux | 5.15 | 5.15.216 |
| Linux | 6.1 | 6.1.183 |
| Linux | 6.6 | 6.6.148 |
| Linux | 6.12 | 6.12.101 |
| Linux | 6.18 | 6.18.42 |
| Linux | 7.1 | 7.1.5 |
| Linux | later releases | 7.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.187-1 | DEBIAN-CVE-2026-72119 |
| Debian | 12 | linux-6.12 | 6.12.101-1~deb12u1 | DEBIAN-CVE-2026-72119 |
| Debian | 13 | linux | 6.12.101-1 | DEBIAN-CVE-2026-72119 |
| Debian | 14 | linux | 7.1.5-1 | DEBIAN-CVE-2026-72119 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-72119 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-72119 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-72119 |
| Ubuntu | 22.04:LTS | linux | 5.15.0-198.208 | UBUNTU-CVE-2026-72119 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-aws | 5.15.0-1117.124 | UBUNTU-CVE-2026-72119 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1069.74~22.04.1 | UBUNTU-CVE-2026-72119 USN-9024-1 |
| Ubuntu | 22.04:LTS | linux-azure | 5.15.0-1123.132 | UBUNTU-CVE-2026-72119 USN-8875-1 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1073.82~22.04.1 | UBUNTU-CVE-2026-72119 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde | 5.15.0-1122.131 | UBUNTU-CVE-2026-72119 USN-8876-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1071.78~22.04.1 | UBUNTU-CVE-2026-72119 USN-9026-1 |
| Ubuntu | 22.04:LTS | linux-gcp | 5.15.0-1118.128 | UBUNTU-CVE-2026-72119 USN-8877-1 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1073.81~22.04.1 | UBUNTU-CVE-2026-72119 USN-9024-1 |
| 74 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2026-72119 |
| Alpaquita | 25 | linux-lts | 6.12.103-r0 | BELL-CVE-2026-72119 |
| Alpaquita | stream | linux-lts | 6.18.43-r0 | BELL-CVE-2026-72119 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat rates this Moderate.
CAN BCM TX operation updates can race with bcm_can_tx and bcm_tx_timeout_handler because frame data and timer fields were updated without consistently holding bcm_tx_lock. A local process using CAN_BCM sockets can update an existing TX operation while the timer path is transmitting, so the kernel may observe partially updated or not yet validated CAN frame content and inconsistent timer state. For the CVSS the PR:L because triggering requires local code execution with access to CAN_BCM socket operations, but not full administrative privileges in deployments where CAN interfaces are already available. The issue is not directly reachable over an IP network and is triggered through the local CAN socket control path rather than by remote packet traffic. Impact is at least incorrect CAN frame transmission or local denial of service.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 8 | kernel-rt | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-72119.