Debian Package Tracker
Register | Log in
Subscribe

intel-microcode

Processor microcode firmware for Intel CPUs

Choose email to subscribe with

general
  • source: intel-microcode (non-free-firmware)
  • version: 3.20250512.1
  • maintainer: Henrique de Moraes Holschuh (DMD)
  • uploaders: Giacomo Catenazzi [DMD]
  • arch: amd64 i386 x32
  • std-ver: 4.1.1
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 3.20240813.1~deb11u1
  • o-o-sec: 3.20250512.1~deb11u1
  • o-o-p-u: 3.20240813.1~deb11u1
  • oldstable: 3.20250211.1~deb12u1
  • old-sec: 3.20250512.1~deb12u1
  • old-p-u: 3.20250512.1~deb12u1
  • stable: 3.20250512.1
  • testing: 3.20250512.1
  • unstable: 3.20250512.1
versioned links
  • 3.20240813.1~deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.20250211.1~deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.20250512.1~deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.20250512.1~deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.20250512.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • intel-microcode (15 bugs: 0, 12, 3, 0)
action needed
Debci reports failed tests high
  • unstable: fail (log)
    The tests ran in 0:01:05
    Last run: 2025-08-14T19:10:33.000Z
    Previous status: unknown

  • testing: neutral (log)
    The tests ran in 0:01:08
    Last run: 2025-08-21T13:05:48.000Z
    Previous status: unknown

  • stable: neutral (log)
    The tests ran in 0:00:55
    Last run: 2025-08-20T14:19:35.000Z
    Previous status: unknown

Created: 2025-08-14 Last update: 2025-08-22 18:32
9 security issues in trixie high

There are 9 open security issues in trixie.

9 important issues:
  • CVE-2025-20053: Improper buffer restrictions for some Intel(R) Xeon(R) Processor firmware with SGX enabled may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-20109: Improper Isolation or Compartmentalization in the stream cache mechanism for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.
  • CVE-2025-21090: Missing reference to active allocated resource for some Intel(R) Xeon(R) processors may allow an authenticated user to potentially enable denial of service via local access.
  • CVE-2025-22839: Insufficient granularity of access control in the OOB-MSM for some Intel(R) Xeon(R) 6 Scalable processors may allow a privileged user to potentially enable escalation of privilege via adjacent access.
  • CVE-2025-22840: Sequence of processor instructions leads to unexpected behavior for some Intel(R) Xeon(R) 6 Scalable processors may allow an authenticated user to potentially enable escalation of privilege via local access
  • CVE-2025-22889: Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processor with Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-24305: Insufficient control flow management in the Alias Checking Trusted Module (ACTM) firmware for some Intel(R) Xeon(R) processors may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-26403: Out-of-bounds write in the memory subsystem for some Intel(R) Xeon(R) 6 processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-32086: Improperly implemented security check for standard in the DDRIO configuration for some Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
Created: 2025-08-12 Last update: 2025-08-13 13:30
9 security issues in sid high

There are 9 open security issues in sid.

9 important issues:
  • CVE-2025-20053: Improper buffer restrictions for some Intel(R) Xeon(R) Processor firmware with SGX enabled may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-20109: Improper Isolation or Compartmentalization in the stream cache mechanism for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.
  • CVE-2025-21090: Missing reference to active allocated resource for some Intel(R) Xeon(R) processors may allow an authenticated user to potentially enable denial of service via local access.
  • CVE-2025-22839: Insufficient granularity of access control in the OOB-MSM for some Intel(R) Xeon(R) 6 Scalable processors may allow a privileged user to potentially enable escalation of privilege via adjacent access.
  • CVE-2025-22840: Sequence of processor instructions leads to unexpected behavior for some Intel(R) Xeon(R) 6 Scalable processors may allow an authenticated user to potentially enable escalation of privilege via local access
  • CVE-2025-22889: Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processor with Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-24305: Insufficient control flow management in the Alias Checking Trusted Module (ACTM) firmware for some Intel(R) Xeon(R) processors may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-26403: Out-of-bounds write in the memory subsystem for some Intel(R) Xeon(R) 6 processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-32086: Improperly implemented security check for standard in the DDRIO configuration for some Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
Created: 2025-08-12 Last update: 2025-08-13 13:30
9 security issues in forky high

There are 9 open security issues in forky.

9 important issues:
  • CVE-2025-20053: Improper buffer restrictions for some Intel(R) Xeon(R) Processor firmware with SGX enabled may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-20109: Improper Isolation or Compartmentalization in the stream cache mechanism for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.
  • CVE-2025-21090: Missing reference to active allocated resource for some Intel(R) Xeon(R) processors may allow an authenticated user to potentially enable denial of service via local access.
  • CVE-2025-22839: Insufficient granularity of access control in the OOB-MSM for some Intel(R) Xeon(R) 6 Scalable processors may allow a privileged user to potentially enable escalation of privilege via adjacent access.
  • CVE-2025-22840: Sequence of processor instructions leads to unexpected behavior for some Intel(R) Xeon(R) 6 Scalable processors may allow an authenticated user to potentially enable escalation of privilege via local access
  • CVE-2025-22889: Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processor with Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-24305: Insufficient control flow management in the Alias Checking Trusted Module (ACTM) firmware for some Intel(R) Xeon(R) processors may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-26403: Out-of-bounds write in the memory subsystem for some Intel(R) Xeon(R) 6 processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-32086: Improperly implemented security check for standard in the DDRIO configuration for some Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
Created: 2025-08-12 Last update: 2025-08-13 13:30
9 security issues in bullseye high

There are 9 open security issues in bullseye.

9 important issues:
  • CVE-2025-20053: Improper buffer restrictions for some Intel(R) Xeon(R) Processor firmware with SGX enabled may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-20109: Improper Isolation or Compartmentalization in the stream cache mechanism for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.
  • CVE-2025-21090: Missing reference to active allocated resource for some Intel(R) Xeon(R) processors may allow an authenticated user to potentially enable denial of service via local access.
  • CVE-2025-22839: Insufficient granularity of access control in the OOB-MSM for some Intel(R) Xeon(R) 6 Scalable processors may allow a privileged user to potentially enable escalation of privilege via adjacent access.
  • CVE-2025-22840: Sequence of processor instructions leads to unexpected behavior for some Intel(R) Xeon(R) 6 Scalable processors may allow an authenticated user to potentially enable escalation of privilege via local access
  • CVE-2025-22889: Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processor with Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-24305: Insufficient control flow management in the Alias Checking Trusted Module (ACTM) firmware for some Intel(R) Xeon(R) processors may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-26403: Out-of-bounds write in the memory subsystem for some Intel(R) Xeon(R) 6 processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-32086: Improperly implemented security check for standard in the DDRIO configuration for some Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
Created: 2025-08-12 Last update: 2025-08-13 13:30
9 security issues in bookworm high

There are 9 open security issues in bookworm.

9 important issues:
  • CVE-2025-20053: Improper buffer restrictions for some Intel(R) Xeon(R) Processor firmware with SGX enabled may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-20109: Improper Isolation or Compartmentalization in the stream cache mechanism for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.
  • CVE-2025-21090: Missing reference to active allocated resource for some Intel(R) Xeon(R) processors may allow an authenticated user to potentially enable denial of service via local access.
  • CVE-2025-22839: Insufficient granularity of access control in the OOB-MSM for some Intel(R) Xeon(R) 6 Scalable processors may allow a privileged user to potentially enable escalation of privilege via adjacent access.
  • CVE-2025-22840: Sequence of processor instructions leads to unexpected behavior for some Intel(R) Xeon(R) 6 Scalable processors may allow an authenticated user to potentially enable escalation of privilege via local access
  • CVE-2025-22889: Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processor with Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-24305: Insufficient control flow management in the Alias Checking Trusted Module (ACTM) firmware for some Intel(R) Xeon(R) processors may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-26403: Out-of-bounds write in the memory subsystem for some Intel(R) Xeon(R) 6 processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
  • CVE-2025-32086: Improperly implemented security check for standard in the DDRIO configuration for some Intel(R) Xeon(R) 6 Processors when using Intel(R) SGX or Intel(R) TDX may allow a privileged user to potentially enable escalation of privilege via local access.
Created: 2025-08-12 Last update: 2025-08-13 13:30
5 open merge requests in Salsa normal
There are 5 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.
Created: 2025-08-19 Last update: 2025-08-21 09:32
lintian reports 2 warnings normal
Lintian reports 2 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2025-07-21 Last update: 2025-07-21 22:02
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.2 instead of 4.1.1).
Created: 2018-01-05 Last update: 2025-05-17 18:30
news
[rss feed]
  • [2025-05-25] Accepted intel-microcode 3.20250512.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2025-05-23] Accepted intel-microcode 3.20250512.1~deb12u1 (source) into stable-security (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2025-05-22] intel-microcode 3.20250512.1 MIGRATED to testing (Debian testing watch)
  • [2025-05-18] Accepted intel-microcode 3.20250512.1~deb11u1 (source) into oldstable-security (Tobias Frost)
  • [2025-05-17] Accepted intel-microcode 3.20250512.1 (source) into unstable (Henrique de Moraes Holschuh)
  • [2025-03-29] Accepted intel-microcode 3.20250211.1~deb11u1 (source) into oldstable-security (Tobias Frost)
  • [2025-03-08] Accepted intel-microcode 3.20250211.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2025-02-22] intel-microcode 3.20250211.1 MIGRATED to testing (Debian testing watch)
  • [2025-02-16] Accepted intel-microcode 3.20250211.1 (source) into unstable (Henrique de Moraes Holschuh)
  • [2024-12-23] Accepted intel-microcode 3.20241112.1~deb11u1 (source) into oldstable-security (Tobias Frost)
  • [2024-12-18] Accepted intel-microcode 3.20241112.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2024-11-24] Accepted intel-microcode 3.20240910.1~deb11u1 (source) into oldstable-security (Tobias Frost)
  • [2024-11-20] intel-microcode 3.20241112.1 MIGRATED to testing (Debian testing watch)
  • [2024-11-14] Accepted intel-microcode 3.20241112.1 (source) into unstable (Henrique de Moraes Holschuh)
  • [2024-11-02] Accepted intel-microcode 3.20240910.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2024-09-27] intel-microcode 3.20240910.1 MIGRATED to testing (Debian testing watch)
  • [2024-09-21] Accepted intel-microcode 3.20240910.1 (source) into unstable (Henrique de Moraes Holschuh)
  • [2024-08-22] Accepted intel-microcode 3.20240813.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2024-08-21] Accepted intel-microcode 3.20240813.1~deb11u1 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2024-08-20] intel-microcode 3.20240813.2 MIGRATED to testing (Debian testing watch)
  • [2024-08-20] intel-microcode 3.20240813.2 MIGRATED to testing (Debian testing watch)
  • [2024-08-17] Accepted intel-microcode 3.20240813.2 (source) into unstable (Henrique de Moraes Holschuh)
  • [2024-08-15] Accepted intel-microcode 3.20240813.1 (source) into unstable (Henrique de Moraes Holschuh)
  • [2024-06-19] intel-microcode 3.20240531.1+nmu1 MIGRATED to testing (Debian testing watch)
  • [2024-06-13] Accepted intel-microcode 3.20240531.1+nmu1 (source) into unstable (Chris Hofstaedtler) (signed by: Christian Hofstaedtler)
  • [2024-06-09] Accepted intel-microcode 3.20240514.1~deb11u1 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2024-06-09] Accepted intel-microcode 3.20240514.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
  • [2024-06-07] intel-microcode 3.20240531.1 MIGRATED to testing (Debian testing watch)
  • [2024-06-01] Accepted intel-microcode 3.20240531.1 (source) into unstable (Henrique de Moraes Holschuh)
  • [2024-05-22] intel-microcode 3.20240514.1 MIGRATED to testing (Debian testing watch)
  • 1
  • 2
bugs [bug history graph]
  • all: 18
  • RC: 1
  • I&N: 12
  • M&W: 4
  • F&P: 1
  • patch: 0
links
  • homepage
  • lintian (0, 2)
  • buildd: logs, checks, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 3.20250512.1ubuntu1
  • 39 bugs
  • patches for 3.20250512.1ubuntu1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing