CVE-2024-28956

Published May 13, 2025

Last updated 5 months ago

CVSS medium 5.7
Linux Kernel

Overview

Description
Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution for some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
Source
secure@intel.com
NVD status
Awaiting Analysis

Risk scores

CVSS 4.0

Type
Secondary
Base score
5.7
Impact score
-
Exploitability score
-
Vector string
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Severity
MEDIUM

CVSS 3.1

Type
Secondary
Base score
5.6
Impact score
4
Exploitability score
1.1
Vector string
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
Severity
MEDIUM

Social media

Hype score
Not currently trending

  1. 🔴 Xen Hypervisor Multi-CVE Flaws Patched in Debian Advisory Debian issued DSA-6068-1 for 13 Xen vulnerabilities enabling memory disclosure, DoS, or privilege escalation. CVEs span CVE-2024-28956 through CVE-2025-1713. What's notable: Xen underpins cloud and enterprise

    @the_c_protocol

    3 Dec 2025

    39 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  2. 🚨 Urgent Xen Patch Alert! CVE-2024-28956 (CVSS 5.7) impacts SUSE Linux & openSUSE. Fixes Intel CPU flaws + HPE DL580 boot issues. 🔗Read more: 👉https://t.co/6aUx2Zqmz1 #InfoSec #SysAdmin https://t.co/o2Z82fIpT1

    @Cezar_H_Linux

    26 May 2025

    9 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. URGENT: #Fedora42 users! 🐧 Xen hypervisor XSA-469 (CVE-2024-28956) allows VM escape via indirect branch prediction. Patch NOW: dnf upgrade --advisory FEDORA-2025-b3d59fca78 Read more: 👉 https://t.co/BDl4SWwGXw #Cybersecurity #SysAdmin https://t.co/Y0qEDcAuTf

    @Cezar_H_Linux

    18 May 2025

    60 Impressions

    1 Retweet

    2 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  4. Researchers discovered Intel CPU flaws CVE-2024-28956 and CVE-2025-24495 that leak kernel memory and revive Spectre v2 attacks. Patches are available but the risk spans many modern processors. #IntelSecurity #CPUFlaws #SpectreV2 #MemoryLeak #CyberThreats #DataProtection https://t

    @CloneSystemsInc

    16 May 2025

    49 Impressions

    0 Retweets

    2 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. 💻 Spectre Isn’t Dead. It’s Mutating! New CPU flaw hits ALL modern Intel chips. 🛠 Researchers at ETH Zurich and VUSec uncovered Spectre-style Intel CPU flaws (CVE-2024-45332, CVE-2024-28956, CVE-2025-24495) that leak memory across users, guests, and ... https://t.co/FnN

    @IT_news_for_all

    16 May 2025

    55 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  6. 💻 Spectre Isn’t Dead. It’s Mutating! New CPU flaw hits ALL modern Intel chips. 🛠 Researchers at ETH Zurich and VUSec uncovered Spectre-style Intel CPU flaws (CVE-2024-45332, CVE-2024-28956, CVE-2025-24495) that leak memory across users, guests, and hosts—at rates up

    @TheHackersNews

    16 May 2025

    17623 Impressions

    60 Retweets

    107 Likes

    20 Bookmarks

    1 Reply

    5 Quotes

  7. 🚨 URGENT for #Linux Admins! 🚨 The latest Unbreakable Enterprise Kernel update fixes CVE-2024-28956, a severe x86 security flaw. If you manage cloud servers, financial systems, or Kubernetes clusters, patch now ! Read more: 👉 https://t.co/KSkq0kuKEb #CyberSecurity #DevOp

    @Cezar_H_Linux

    14 May 2025

    15 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  8. CVE-2024-28956, これも Intel CPU でだけ投機的実行でホストのメモリが推測できるかもみたいなやつかあ https://t.co/6VQyWaAqyg

    @apstndb

    12 May 2025

    44 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  9. Compute Engine update on May 12, 2025 https://t.co/hXL9uJsr2F #googlecloud A vulnerability (CVE-2024-28956) affecting Intel Cascade Lake processors and Intel Ice Lake processors was discovered and is being addressed 1/3

    @gcpweekly

    12 May 2025

    54 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

Related CVEs

  1. In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value. __xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list.•CVE-2025-39965
  2. In the Linux kernel, the following vulnerability has been resolved: tls: make sure to abort the stream if headers are bogus Normally we wait for the socket to buffer up the whole record before we service it. If the socket has a tiny buffer, however, we read out the data sooner, to prevent connection stalls. Make sure that we abort the connection when we find out late that the record is actually invalid. Retrying the parsing is fine in itself but since we copy some more data each time before we parse we can overflow the allocated skb space. Constructing a scenario in which we're under pressure without enough data in the socket to parse the length upfront is quite hard. syzbot figured out a way to do this by serving us the header in small OOB sends, and then filling in the recvbuf with a large normal send. Make sure that tls_rx_msg_size() aborts strp, if we reach an invalid record there's really no way to recover.•CVE-2025-39946
  3. In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.•CVE-2024-58240
  4. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using ->NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.•CVE-2023-4130
  5. In the Linux kernel, the following vulnerability has been resolved: HID: core: do not bypass hid_hw_raw_request hid_hw_raw_request() is actually useful to ensure the provided buffer and length are valid. Directly calling in the low level transport driver function bypassed those checks and allowed invalid paramto be used.•CVE-2025-38494

References

Sources include official advisories and independent security research.