amd64-microcode - Debian Package Tracker

general

source: amd64-microcode (non-free-firmware)
version: 3.20251202.1
maintainer: Henrique de Moraes Holschuh (DMD)
uploaders: Giacomo Catenazzi [DMD]
arch: amd64 i386 x32
std-ver: 3.9.8
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.20240820.1~deb11u1
o-o-sec: 3.20250311.1~deb11u1
o-o-p-u: 3.20240820.1~deb11u1
oldstable: 3.20250311.1~deb12u1
old-sec: 3.20230719.1~deb12u1
stable: 3.20250311.1
testing: 3.20251202.1
unstable: 3.20251202.1

versioned links

3.20230719.1~deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.20240820.1~deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.20250311.1~deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.20250311.1~deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.20250311.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.20251202.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

amd64-microcode (11 bugs: 0, 10, 1, 0)

action needed

11 security issues in trixie high

There are 11 open security issues in trixie.

10 important issues:

CVE-2025-0033: Improper access control within AMD SEV-SNP could allow an admin privileged attacker to write to the RMP during SNP initialization, potentially resulting in a loss of SEV-SNP guest memory integrity.
CVE-2024-36350: A transient execution vulnerability in some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information.
CVE-2024-36357: A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.
CVE-2025-29934: A bug within some AMD CPUs could allow a local admin-privileged attacker to run a SEV-SNP guest using stale TLB entries, potentially resulting in loss of data integrity.
CVE-2025-29943: Write what were condition within AMD CPUs may allow an admin-privileged attacker to modify the configuration of the CPU pipeline potentially resulting in the corruption of the stack pointer inside an SEV-SNP guest.
CVE-2025-48514: Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to attack SNP guest, potentially resulting in a loss of confidentiality.
CVE-2025-48517: Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to create a SEV-ES guest with an ASID in the range meant for SEV-SNP guests potentially resulting in a partial loss of confidentiality.
CVE-2025-52534: Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integrity.
CVE-2025-52536: Improper Prevention of Lock Bit Modification in SEV firmware could allow a privileged attacker to downgrade firmware potentially resulting in a loss of integrity.
CVE-2025-54514: Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.

1 ignored issue:

CVE-2025-62626: Improper handling of insufficient entropy in the AMD CPUs could allow a local attacker to influence the values returned by the RDSEED instruction, potentially resulting in the consumption of insufficiently random values.

Created: 2025-07-08 Last update: 2026-02-11 05:00

7 security issues in sid high

There are 7 open security issues in sid.

7 important issues:

CVE-2025-0033: Improper access control within AMD SEV-SNP could allow an admin privileged attacker to write to the RMP during SNP initialization, potentially resulting in a loss of SEV-SNP guest memory integrity.
CVE-2025-29934: A bug within some AMD CPUs could allow a local admin-privileged attacker to run a SEV-SNP guest using stale TLB entries, potentially resulting in loss of data integrity.
CVE-2025-48514: Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to attack SNP guest, potentially resulting in a loss of confidentiality.
CVE-2025-48517: Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to create a SEV-ES guest with an ASID in the range meant for SEV-SNP guests potentially resulting in a partial loss of confidentiality.
CVE-2025-52534: Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integrity.
CVE-2025-52536: Improper Prevention of Lock Bit Modification in SEV firmware could allow a privileged attacker to downgrade firmware potentially resulting in a loss of integrity.
CVE-2025-54514: Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.

Created: 2025-07-08 Last update: 2026-02-11 05:00

7 security issues in forky high

There are 7 open security issues in forky.

7 important issues:

CVE-2025-0033: Improper access control within AMD SEV-SNP could allow an admin privileged attacker to write to the RMP during SNP initialization, potentially resulting in a loss of SEV-SNP guest memory integrity.
CVE-2025-29934: A bug within some AMD CPUs could allow a local admin-privileged attacker to run a SEV-SNP guest using stale TLB entries, potentially resulting in loss of data integrity.
CVE-2025-48514: Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to attack SNP guest, potentially resulting in a loss of confidentiality.
CVE-2025-48517: Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to create a SEV-ES guest with an ASID in the range meant for SEV-SNP guests potentially resulting in a partial loss of confidentiality.
CVE-2025-52534: Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integrity.
CVE-2025-52536: Improper Prevention of Lock Bit Modification in SEV firmware could allow a privileged attacker to downgrade firmware potentially resulting in a loss of integrity.
CVE-2025-54514: Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.

Created: 2025-08-09 Last update: 2026-02-11 05:00

11 security issues in bullseye high

There are 11 open security issues in bullseye.

11 important issues:

CVE-2025-0033: Improper access control within AMD SEV-SNP could allow an admin privileged attacker to write to the RMP during SNP initialization, potentially resulting in a loss of SEV-SNP guest memory integrity.
CVE-2024-36350: A transient execution vulnerability in some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information.
CVE-2024-36357: A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.
CVE-2025-29934: A bug within some AMD CPUs could allow a local admin-privileged attacker to run a SEV-SNP guest using stale TLB entries, potentially resulting in loss of data integrity.
CVE-2025-29943: Write what were condition within AMD CPUs may allow an admin-privileged attacker to modify the configuration of the CPU pipeline potentially resulting in the corruption of the stack pointer inside an SEV-SNP guest.
CVE-2025-48514: Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to attack SNP guest, potentially resulting in a loss of confidentiality.
CVE-2025-48517: Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to create a SEV-ES guest with an ASID in the range meant for SEV-SNP guests potentially resulting in a partial loss of confidentiality.
CVE-2025-52534: Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integrity.
CVE-2025-52536: Improper Prevention of Lock Bit Modification in SEV firmware could allow a privileged attacker to downgrade firmware potentially resulting in a loss of integrity.
CVE-2025-54514: Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.
CVE-2025-62626: Improper handling of insufficient entropy in the AMD CPUs could allow a local attacker to influence the values returned by the RDSEED instruction, potentially resulting in the consumption of insufficiently random values.

Created: 2025-07-08 Last update: 2026-02-11 05:00

11 security issues in bookworm high

There are 11 open security issues in bookworm.

10 important issues:

CVE-2025-0033: Improper access control within AMD SEV-SNP could allow an admin privileged attacker to write to the RMP during SNP initialization, potentially resulting in a loss of SEV-SNP guest memory integrity.
CVE-2024-36350: A transient execution vulnerability in some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information.
CVE-2024-36357: A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.
CVE-2025-29934: A bug within some AMD CPUs could allow a local admin-privileged attacker to run a SEV-SNP guest using stale TLB entries, potentially resulting in loss of data integrity.
CVE-2025-29943: Write what were condition within AMD CPUs may allow an admin-privileged attacker to modify the configuration of the CPU pipeline potentially resulting in the corruption of the stack pointer inside an SEV-SNP guest.
CVE-2025-48514: Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to attack SNP guest, potentially resulting in a loss of confidentiality.
CVE-2025-48517: Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to create a SEV-ES guest with an ASID in the range meant for SEV-SNP guests potentially resulting in a partial loss of confidentiality.
CVE-2025-52534: Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integrity.
CVE-2025-52536: Improper Prevention of Lock Bit Modification in SEV firmware could allow a privileged attacker to downgrade firmware potentially resulting in a loss of integrity.
CVE-2025-54514: Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.

1 ignored issue:

CVE-2025-62626: Improper handling of insufficient entropy in the AMD CPUs could allow a local attacker to influence the values returned by the RDSEED instruction, potentially resulting in the consumption of insufficiently random values.

Created: 2025-07-08 Last update: 2026-02-11 05:00

Standards version of the package is outdated. high

The package is severely out of date with respect to the Debian Policy. The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.3 instead of 3.9.8).

Created: 2023-05-16 Last update: 2025-12-23 20:00

1 new commit since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 6f4e8e238a95fe7b250e492409dd78915d1aafc7
Author: Henrique de Moraes Holschuh <[email protected]>
Date:   Sat Dec 6 12:22:43 2025 -0300

    NEWS.Debian: correct version tag for latest entry
    
    Package version 3.20251030.1 was never pushed to the archive, change the
    NEWS.Debian tag to a version that is actually present in the changelog.

Created: 2025-10-20 Last update: 2026-03-11 05:18

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-12-07 11:30

4 open merge requests in Salsa normal

There are 4 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2025-09-22 Last update: 2025-09-22 16:04

news

[rss feed]

[2025-12-12] amd64-microcode 3.20251202.1 MIGRATED to testing (Debian testing watch)
[2025-12-06] Accepted amd64-microcode 3.20251202.1 (source) into unstable (Henrique de Moraes Holschuh)
[2025-06-21] Accepted amd64-microcode 3.20250311.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
[2025-03-31] Accepted amd64-microcode 3.20250311.1~deb11u1 (source) into oldstable-security (Tobias Frost)
[2025-03-29] amd64-microcode 3.20250311.1 MIGRATED to testing (Debian testing watch)
[2025-03-24] Accepted amd64-microcode 3.20250311.1 (source) into unstable (Henrique de Moraes Holschuh)
[2024-08-24] Accepted amd64-microcode 3.20240820.1~deb11u1 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
[2024-08-24] Accepted amd64-microcode 3.20240820.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
[2024-08-24] amd64-microcode 3.20240820.1 MIGRATED to testing (Debian testing watch)
[2024-08-24] amd64-microcode 3.20240820.1 MIGRATED to testing (Debian testing watch)
[2024-08-22] Accepted amd64-microcode 3.20240820.1 (source) into unstable (Henrique de Moraes Holschuh)
[2024-08-21] Accepted amd64-microcode 3.20240710.2~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
[2024-08-21] Accepted amd64-microcode 3.20240710.2~deb11u1 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
[2024-08-14] amd64-microcode 3.20240710.2 MIGRATED to testing (Debian testing watch)
[2024-08-12] Accepted amd64-microcode 3.20240710.2 (source) into unstable (Henrique de Moraes Holschuh)
[2024-08-11] Accepted amd64-microcode 3.20240710.1 (source) into unstable (Henrique de Moraes Holschuh)
[2024-06-19] amd64-microcode 3.20240116.2+nmu1 MIGRATED to testing (Debian testing watch)
[2024-06-13] Accepted amd64-microcode 3.20240116.2+nmu1 (source) into unstable (Chris Hofstaedtler) (signed by: Christian Hofstaedtler)
[2024-03-08] amd64-microcode 3.20240116.2 MIGRATED to testing (Debian testing watch)
[2024-03-02] Accepted amd64-microcode 3.20240116.2 (source) into unstable (Henrique de Moraes Holschuh)
[2023-10-27] amd64-microcode 3.20231019.1 MIGRATED to testing (Debian testing watch)
[2023-10-21] Accepted amd64-microcode 3.20231019.1 (source) into unstable (Henrique de Moraes Holschuh)
[2023-10-18] amd64-microcode 3.20230823.1 MIGRATED to testing (Debian testing watch)
[2023-10-13] Accepted amd64-microcode 3.20230823.1 (source) into unstable (Henrique de Moraes Holschuh)
[2023-10-01] Accepted amd64-microcode 3.20230808.1.1~deb11u1 (source amd64) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
[2023-10-01] Accepted amd64-microcode 3.20230808.1.1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Henrique de Moraes Holschuh)
[2023-08-12] amd64-microcode 3.20230808.1.1 MIGRATED to testing (Debian testing watch)
[2023-08-10] Accepted amd64-microcode 3.20230808.1.1 (source) into unstable (Henrique de Moraes Holschuh)
[2023-08-10] Accepted amd64-microcode 3.20230808.1 (source) into unstable (Henrique de Moraes Holschuh)
[2023-07-31] Accepted amd64-microcode 3.20230719.1~deb10u1 (source amd64) into oldoldstable (Jochen Sprickerhof)

bugs [bug history graph]

all: 11 12
RC: 0
I&N: 9 10
M&W: 2
F&P: 0
patch: 0

links

lintian (0, 2)
buildd: logs, cross
popcon
browse source code
edit tags
other distros
security tracker

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.20251202.1ubuntu1
4 bugs
patches for 3.20251202.1ubuntu1