https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-05T07:21:35.008585+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-23225 Withdrawn: BELL-CVE-2026-23225 — CVE-2026-23225 does not affect BellSoft software 2026-10-05T07:21:35.016478+00:00

Withdrawn by the publisher.

https://cve.radiocsirt.org/vuln/certfr-2026-avi-0215 certfr-2026-avi-0215 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu… 2026-10-05T07:21:35.016517+00:00 certfr-2026-avi-0215 https://cve.radiocsirt.org/vuln/euvd-2026-347615 EUVD-2026-347615 2026-10-05T07:21:35.016535+00:00 EUVD-2026-347615 https://cve.radiocsirt.org/vuln/fkie_cve-2026-23225 fkie_cve-2026-23225 2026-10-05T07:21:35.016548+00:00

In the Linux kernel, the following vulnerability has been resolved:

sched/mmcid: Don't assume CID is CPU owned on mode switch

Shinichiro reported a KASAN UAF, which is actually an out of bounds access in the MMCID management code.

CPU0 CPU1 T1 runs in userspace T0: fork(T4) -> Switch to per CPU CID mode fixup() set MM_CID_TRANSIT on T1/CPU1 T4 exit() T3 exit() T2 exit() T1 exit() switch to per task mode ---> Out of bounds access.

As T1 has not scheduled after T0 set the TRANSIT bit, it exits with the TRANSIT bit set. sched_mm_cid_remove_user() clears the TRANSIT bit in the task and drops the CID, but it does not touch the per CPU storage. That's functionally correct because a CID is only owned by the CPU when the ONCPU bit is set, which is mutually exclusive with the TRANSIT flag.

Now sched_mm_cid_exit() assumes that the CID is CPU owned because the prior mode was per CPU. It invokes mm_drop_cid_on_cpu() which clears the not set ONCPU bit and then invokes clear_bit() with an insanely large bit number because TRANSIT is set (bit 29).

Prevent that by actually validating that the CID is CPU owned in mm_drop_cid_on_cpu().

 https://cve.radiocsirt.org/vuln/ghsa-p525-h9pq-233r GHSA-p525-h9pq-233r 2026-10-05T07:21:35.016587+00:00

In the Linux kernel, the following vulnerability has been resolved:

sched/mmcid: Don't assume CID is CPU owned on mode switch

Shinichiro reported a KASAN UAF, which is actually an out of bounds access in the MMCID management code.

CPU0 CPU1 T1 runs in userspace T0: fork(T4) -> Switch to per CPU CID mode fixup() set MM_CID_TRANSIT on T1/CPU1 T4 exit() T3 exit() T2 exit() T1 exit() switch to per task mode ---> Out of bounds access.

As T1 has not scheduled after T0 set the TRANSIT bit, it exits with the TRANSIT bit set. sched_mm_cid_remove_user() clears the TRANSIT bit in the task and drops the CID, but it does not touch the per CPU storage. That's functionally correct because a CID is only owned by the CPU when the ONCPU bit is set, which is mutually exclusive with the TRANSIT flag.

Now sched_mm_cid_exit() assumes that the CID is CPU owned because the prior mode was per CPU. It invokes mm_drop_cid_on_cpu() which clears the not set ONCPU bit and then invokes clear_bit() with an insanely large bit number because TRANSIT is set (bit 29).

Prevent that by actually validating that the CID is CPU owned in mm_drop_cid_on_cpu().

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-23225 msrc_CVE-2026-23225 — sched/mmcid: Don't assume CID is CPU owned on mode switch 2026-10-05T07:21:35.016613+00:00 msrc_CVE-2026-23225 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10387-1 openSUSE-SU-2026:10387-1 — kernel-devel-6.19.8-1.1 on GA media 2026-10-05T07:21:35.016629+00:00

kernel-devel-6.19.8-1.1 on GA media

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23225 UBUNTU-CVE-2026-23225 2026-10-05T07:21:35.016654+00:00

Affected: Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 82 more

In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Don't assume CID is CPU owned on mode switch Shinichiro reported a KASAN UAF, which is actually an out of bounds access in the MMCID management code. CPU0 CPU1 T1 runs in userspace T0: fork(T4) -> Switch to per CPU CID mode fixup() set MM_CID_TRANSIT on T1/CPU1 T4 exit() T3 exit() T2 exit() T1 exit() switch to per task mode ---> Out of bounds access. As T1 has not scheduled after T0 set the TRANSIT bit, it exits with the TRANSIT bit set. sched_mm_cid_remove_user() clears the TRANSIT bit in the task and drops the CID, but it does not touch the per CPU storage. That's functionally correct because a CID is only owned by the CPU when the ONCPU bit is set, which is mutually exclusive with the TRANSIT flag. Now sched_mm_cid_exit() assumes that the CID is CPU owned because the prior mode was per CPU. It invokes mm_drop_cid_on_cpu() which clears the not set ONCPU bit and then invokes clear_bit() with an insanely large bit number because TRANSIT is set (bit 29). Prevent that by actually validating that the CID is CPU owned in mm_drop_cid_on_cpu().

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0462 WID-SEC-W-2026-0462 — Linux Kernel: Mehrere Schwachstellen 2026-10-05T07:21:35.016768+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.