Vulnerability · Published Aug 10, 2026 · Assigned by Linux
CVE-2026-68138net/sched: serialize qdisc_rtab_list against concurrent get/put
High 7.8
In plain English
A high-severity race condition in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 13% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code. Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: net/sched: serialize qdisc_rtab_list against concurrent get/put qdisc_get_rtab() and qdisc_put_rtab() mutate the process-global singly linked list qdisc_rtab_list and a plain non-atomic 'int refcnt' with no lock. This was only safe because every caller historically held the RTNL mutex, which serialized all rate-table lookups, inserts and frees. That invariant no longer holds. cls_flower sets TCF_PROTO_OPS_DOIT_UNLOCKED, so tc_new_tfilter() keeps rtnl_held == false for it and sets TCA_ACT_FLAGS_NO_RTNL. That flag propagates through tcf_exts_validate_ex() -> tcf_action_init() -> tcf_action_init_1() -> tcf_police_init(), which calls qdisc_get_rtab()/qdisc_put_rtab() with the RTNL mutex NOT held. Two RTM_NEWTFILTER requests on different CPUs, each adding a flower filter with a police action carrying the same rate, then race on qdisc_rtab_list and on the non-atomic refcnt, leading to a use-after-free / double-free of the kmalloc-2k struct qdisc_rate_table. qdisc_rtab_list is a single global (not per-netns), so the corrupted object is shared system-wide. BUG: KASAN: slab-use-after-free in qdisc_put_rtab+0x12f/0x160 qdisc_put_rtab+0x12f/0x160 tcf_police_init+0xda9/0x1590 tcf_action_init_1+0x460/0x6b0 tcf_action_init+0x439/0xa40 tcf_exts_validate_ex+0x42d/0x550 fl_change+0xddd/0x7da0 tc_new_tfilter+0xaa7/0x2420 rtnetlink_rcv_msg+0x95e/0xe90 which belongs to the cache kmalloc-2k of size 2048 Protect qdisc_rtab_list and the refcount with a dedicated spinlock. The (sleeping, GFP_KERNEL) allocation in qdisc_get_rtab() is performed before taking the lock; if a concurrent inserter added an identical table in the meantime the freshly allocated one is freed under the lock, so no duplicate is leaked. qdisc_put_rtab() now decrements the refcount and unlinks under the same lock.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:8 | bpftool | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-abi-stablelists | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-core | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-cross-headers | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-debug | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-debug-core | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-debug-devel | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-debug-modules | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-debug-modules-extra | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-devel | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-doc | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-headers | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-modules | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-modules-extra | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-rt | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-core | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-debug | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-debug-core | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-debug-devel | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-debug-modules | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-devel | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-modules | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-rt-modules-extra | 4.18.0-553.178.1.rt7.519.el8_10 | ALSA-2026:89082 |
| AlmaLinux:8 | kernel-tools | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-tools-libs | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-tools-libs-devel | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-zfcpdump | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-zfcpdump-core | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-zfcpdump-devel | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-zfcpdump-modules | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | kernel-zfcpdump-modules-extra | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | perf | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| AlmaLinux:8 | python3-perf | 4.18.0-553.178.1.el8_10 | ALSA-2026:89083 |
| Debian:12 | linux | 6.1.187-1 | DEBIAN-CVE-2026-68138 |
| Debian:13 | linux | 6.12.105-1 | DEBIAN-CVE-2026-68138 |
| Debian:14 | linux | 7.1.6-1 | DEBIAN-CVE-2026-68138 |
| Debian:12 | linux-6.12 | 6.12.107-1~deb12u1 | DEBIAN-CVE-2026-68138 |
| Rocky Linux:8 | kernel | 0:4.18.0-553.178.1.el8_10 | RLSA-2026:89083 |
| Rocky Linux:8 | kernel-rt | 0:4.18.0-553.178.1.rt7.519.el8_10 | RLSA-2026:89082 |
| Ubuntu:22.04:LTS | linux | 5.15.0-202.212 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux | 7.0.0-38.38 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1119.126 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1014.14 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1125.134 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1017.17 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1017.17~24.04.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1124.133 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1016.16 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1120.130 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1014.14 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1115.121 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1008.9 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1102.110 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-38.38~24.04.4 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1113.117 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1015.15 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1114.120 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1111.116 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-197.207 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1114.115 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1024.25~24.04.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2022.23 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1070.72 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1035.38 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1059.59 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1015.15 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1116.122 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1013.13 | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-38.38.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-38.38.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-38.38.1~24.04.1 | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-vmware | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:24.04:LTS | linux-xilinx | no fix listed | UBUNTU-CVE-2026-68138 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | no fix listed | UBUNTU-CVE-2026-68138 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 470502de5bdb1ed0def643a4458593a40b8f6b66 – before 1b050d09dd1a0ddae83bf012cf4956b7a960235f470502de5bdb1ed0def643a4458593a40b8f6b66 – before 6e0241f6cbb149d926ee8efee2c734fea71452cf470502de5bdb1ed0def643a4458593a40b8f6b66 – before f93c89392bd3b180b5b7abc6fdae8e3dd667a313470502de5bdb1ed0def643a4458593a40b8f6b66 – before 4131dd0b6f67acddd616ed7c244e1d3eedd46e7b470502de5bdb1ed0def643a4458593a40b8f6b66 – before d981098b76756ed71666a27518eeb69883657c43470502de5bdb1ed0def643a4458593a40b8f6b66 – before 8ddc2eb0d2da9c83f54f1e5720525b461b8480c4470502de5bdb1ed0def643a4458593a40b8f6b66 – before fb29e1b41052488ee3f2d115d4a870497ebd7f7d470502de5bdb1ed0def643a4458593a40b8f6b66 – before f43ee0c0730d6191629b5ee1ceae27b1ebfdc047 |
| Linux | Linux | 5.1 |
Weakness: CWE-362 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
- https://git.kernel.org/stable/c/1b050d09dd1a0ddae83bf012cf4956b7a960235f
- https://git.kernel.org/stable/c/6e0241f6cbb149d926ee8efee2c734fea71452cf
- https://git.kernel.org/stable/c/f93c89392bd3b180b5b7abc6fdae8e3dd667a313
- https://git.kernel.org/stable/c/4131dd0b6f67acddd616ed7c244e1d3eedd46e7b
- https://git.kernel.org/stable/c/d981098b76756ed71666a27518eeb69883657c43
- https://git.kernel.org/stable/c/8ddc2eb0d2da9c83f54f1e5720525b461b8480c4
- https://git.kernel.org/stable/c/fb29e1b41052488ee3f2d115d4a870497ebd7f7d
- https://git.kernel.org/stable/c/f43ee0c0730d6191629b5ee1ceae27b1ebfdc047