[Git][security-tracker-team/security-tracker][master] Track fixes for intel-microcode via unstable

[Salvatore Bonaccorso (@carnil)]

Salvatore Bonaccorso pushed to branch master at Debian Security Tracker / security-tracker


Commits:
a209fbf6 by Salvatore Bonaccorso at 2026-11-04T20:34:20+01:00
Track fixes for intel-microcode via unstable

- - - - -


1 changed file:

- data/CVE/list


Changes:

=====================================
data/CVE/list
=====================================
@@ -120287,55 +120287,55 @@ CVE-2020-37257
 CVE-2016-20097 (Weaver (Fanwei) E-cology 8.0 contains a SQL injection vulnerability in ...)
 	NOT-FOR-US: Weaver E-cology
 CVE-2026-20707 (Hardware logic contains race conditions for some 3rd Gen Intel(R) Xeon ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
 	NOTE: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01443.html
 CVE-2026-20901 (Improper input validation for some Intel(R) Xeon(R) processors within  ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
 	NOTE: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01442.html
 CVE-2026-20713 (Always-incorrect control flow implementation in some firmware for some ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
 	NOTE: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01442.html
 CVE-2026-20760 (Improper handling of overlap between protected memory ranges in some m ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
 	NOTE: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01441.html
 CVE-2026-20716 (Improper access control for some Intel(R) Processors within Ring 3: Us ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
 	NOTE: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01435.html
 CVE-2025-35973 (Improper handling of values for some Intel(R) Processors within Ring 0 ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
 	NOTE: https://www.cve.org/CVERecord?id=CVE-2025-35973
 CVE-2026-20917 (Exposure of sensitive information caused by incorrect data forwarding  ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
 	NOTE: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01423.html
 CVE-2025-31938 (Insufficient granularity of access control in some subsystem for some  ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
 	NOTE: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01404.html
 CVE-2025-31936 (Improper handling of overlap between protected memory ranges for some  ...)
-	- intel-microcode <unfixed> (bug #1144158)
+	- intel-microcode 3.20260925.1 (bug #1144158)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	NOTE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260811
@@ -195427,7 +195427,7 @@ CVE-2025-35991 (Improper initialization in the UEFI firmware for some Intel plat
 CVE-2025-35990 (Improper input validation for some Intel Endpoint Management Assistant ...)
 	NOT-FOR-US: Intel
 CVE-2025-35979 (Exposure of sensitive information caused by shared microarchitectural  ...)
-	- intel-microcode <unfixed> (bug #1137032)
+	- intel-microcode 3.20260925.1 (bug #1137032)
 	[trixie] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bookworm] - intel-microcode <postponed> (As usual fixed top-down, expose first in unstable, then likely point release)
 	[bullseye] - intel-microcode <postponed> (Wait for stable update)



View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/a209fbf6f306069da98fc222490a3d26892e60c5

-- 
View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/a209fbf6f306069da98fc222490a3d26892e60c5
You're receiving this email because of your account on salsa.debian.org. Manage all notifications: https://salsa.debian.org/-/profile/notifications | Help: https://salsa.debian.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-security-tracker-commits/attachments/20261104/be5ae7ce/attachment.htm>