Pop-Up Thingie

>>> Magnum BBS <<<
  • Home
  • Forum
  • Files
  • Log in

  1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC
  • Bug#1109035: amd64-microcode: 2024-36350/TSA-SQ and CVE-2024-36357/TSA-

    From Salvatore Bonaccorso@21:1/5 to Salvatore Bonaccorso on Sat Jul 19 23:10:01 2025
    Hi Henrique,

    On Thu, Jul 10, 2025 at 09:12:23AM +0200, Salvatore Bonaccorso wrote:
    Source: amd64-microcode
    Version: 3.20250311.1
    Severity: grave
    Tags: security upstream
    X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>
    Control: found -1 3.20250311.1~deb12u1

    Hi Henrique,

    The following vulnerabilities were published for amd64-microcode.

    CVE-2024-36350[0]:
    | 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[1]:
    | 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.

    My understanding from the patch levels in amd-ucode/README is that we
    are not yet covered by the needed updates on microcode side[2] for CVE-2024-36350/TSA-SQ and CVE-2024-36357/TSA-L1 in amd64-microcode/3.20250311.1. Correct?

    If you fix the vulnerabilities please also make sure to include the
    CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

    For further information see:

    [0] https://security-tracker.debian.org/tracker/CVE-2024-36350
    https://www.cve.org/CVERecord?id=CVE-2024-36350
    [1] https://security-tracker.debian.org/tracker/CVE-2024-36357
    https://www.cve.org/CVERecord?id=CVE-2024-36357
    [2] https://www.amd.com/content/dam/amd/en/documents/resources/bulletin/technical-guidance-for-mitigating-transient-scheduler-attacks.pdf

    If not wrong, those updates might be included in https://gitlab.com/kernel-firmware/linux-firmware/-/commit/331eac9144402d6cfa02ff3b2888a40bb9a7a01a

    Is this correct?

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Salvatore Bonaccorso@21:1/5 to Salvatore Bonaccorso on Wed Jul 30 14:00:01 2025
    Hi Henrique,

    On Sat, Jul 19, 2025 at 10:59:33PM +0200, Salvatore Bonaccorso wrote:
    Hi Henrique,

    On Thu, Jul 10, 2025 at 09:12:23AM +0200, Salvatore Bonaccorso wrote:
    Source: amd64-microcode
    Version: 3.20250311.1
    Severity: grave
    Tags: security upstream
    X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>
    Control: found -1 3.20250311.1~deb12u1

    Hi Henrique,

    The following vulnerabilities were published for amd64-microcode.

    CVE-2024-36350[0]:
    | 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[1]:
    | 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.

    My understanding from the patch levels in amd-ucode/README is that we
    are not yet covered by the needed updates on microcode side[2] for CVE-2024-36350/TSA-SQ and CVE-2024-36357/TSA-L1 in amd64-microcode/3.20250311.1. Correct?

    If you fix the vulnerabilities please also make sure to include the
    CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

    For further information see:

    [0] https://security-tracker.debian.org/tracker/CVE-2024-36350
    https://www.cve.org/CVERecord?id=CVE-2024-36350
    [1] https://security-tracker.debian.org/tracker/CVE-2024-36357
    https://www.cve.org/CVERecord?id=CVE-2024-36357
    [2] https://www.amd.com/content/dam/amd/en/documents/resources/bulletin/technical-guidance-for-mitigating-transient-scheduler-attacks.pdf

    If not wrong, those updates might be included in https://gitlab.com/kernel-firmware/linux-firmware/-/commit/331eac9144402d6cfa02ff3b2888a40bb9a7a01a

    Is this correct?

    Will potentially as well need https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=3768c184de68a85b9df6697e7f93a2f61de90a99
    ?

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Henrique de Moraes Holschuh@21:1/5 to All on Thu Jul 31 23:00:01 2025
    Hello Salvatore,

    I will look into it soon, but I am swamped with work so it could take a week or two for me to upload anything .

    As far as I know, we cannot update much of the AMD fleet (computers that did not get firmware updates to switch to the new microcode signature track) anyway, so I will also need to check if this changed somehow, etc.

    --
    Henrique de Moraes Holschuh <[email protected]>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • Who's Online

  • Recent Visitors

    • Krenn
      Sun Jun 7 03:07:26 2026
      from Sydney, Nsw via Telnet
    • Krenn
      Sun Jun 7 01:30:12 2026
      from Sydney, Nsw via Telnet
    • Centurion
      Sat Jun 6 23:27:30 2026
      from Berea, Ohio via Telnet
    • Ab Cadd
      Sat Jun 6 15:42:53 2026
      from Sheboygan, Wi via Telnet
    • Centurion
      Sat Jun 6 15:32:28 2026
      from Berea, Ohio via Telnet
    • Krenn
      Sat Jun 6 11:38:56 2026
      from Sydney, Nsw via Telnet
    • Furryboy
      Sat Jun 6 10:56:29 2026
      from Romania, Galati via SSH
    • Centurion
      Fri Jun 5 22:28:01 2026
      from Berea, Ohio via Telnet
  • System Info

    Sysop: Keyop
    Location: Huddersfield, West Yorkshire, UK
    Users: 715
    Nodes: 16 (2 / 14)
    Uptime: 159:00:47
    Calls: 12,094
    Calls today: 2
    Files: 15,000
    Messages: 6,517,759

© >>> Magnum BBS <<<, 2026