CVE-2025-37899

Published May 20, 2025

Last updated 5 days ago

CVSS high 8.8
Linux Kernel

Overview

AI description

Automated description summarized from trusted sources.

CVE-2025-37899 is a use-after-free vulnerability found in the ksmbd component of the Linux kernel, which is an in-kernel server implementing the SMB3 protocol for file sharing over networks. Specifically, the vulnerability exists in the session logoff handler. The vulnerability occurs because the `sess->user` object can be freed by one thread processing a logoff command while another thread, handling a new connection's session setup request, might still be accessing the same `sess->user` object. This concurrent access can lead to memory corruption and potentially allow attackers to execute arbitrary code with kernel privileges.

Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in session logoff The sess->user object can currently be in use by another thread, for example if another connection has sent a session setup request to bind to the session being free'd. The handler for that connection could be in the smb2_sess_setup function which makes use of sess->user.
Source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD status
Modified
Products
linux_kernel

Risk scores

CVSS 3.1

Type
Primary
Base score
7.8
Impact score
5.9
Exploitability score
1.8
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity
HIGH

Weaknesses

nvd@nist.gov
CWE-416

Social media

Hype score
Not currently trending
  1. Slice: SAST + LLM Interprocedural Context Extractor Amazing article by @noperator about combining the use of CodeQL and LLMs to reliably rediscover CVE-2025-37899 — a remotely-triggerable vulnerability in the ksmbd module. https://t.co/jnC9xZlkNw https://t.co/Uipd61qRaM

    @linkersec

    18 Nov 2025

    2409 Impressions

    7 Retweets

    22 Likes

    16 Bookmarks

    1 Reply

    0 Quotes

  2. as i read more i realise, RL in security seems untapped. a self-adjusting RL env designed to adapt and counter the trivial attacks. now, think the reverse when used in adversarial. @seanhn 's CVE-2025-37899 was a crazy demonstration when i read. hacking is RLable now.

    @ShubhamKukretii

    22 Sept 2025

    281 Impressions

    0 Retweets

    9 Likes

    2 Bookmarks

    1 Reply

    0 Quotes

  3. Exploiting a Use-After-Free Vulnerability in the Linux Kernel SMB Server (CVE-2025-37899) Here's a breakdown of a race condition leading to use-after-free in ksmbd's SMB2 logoff handler. This allows remote kernel memory corruption via concurrent connections bound to the same htt

    @datareaperai

    12 Sept 2025

    578 Impressions

    2 Retweets

    18 Likes

    8 Bookmarks

    1 Reply

    0 Quotes

  4. 🚨 CVE-2025-37899 Alert 🚨 A new Linux Kernel SMB Zero-Day puts millions of systems at risk of remote exploitation. ⚠ Patch immediately to prevent unauthorized access and data compromise. 🔒 Stay secure with CyberSNR 👉 https://t.co/Uc4Ulzyrel #CyberSecurity #ZeroDay h

    @CyberSNR

    30 Aug 2025

    1 Impression

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. Zero day in Linux kernel’s SMB (CVE-2025-37899) using LLMs (OpenAI’s o3) https://t.co/1UdtbL2MhZ Credits @seanhn #infosec #llm https://t.co/7h6OCBHHjG

    @0xor0ne

    26 Aug 2025

    9146 Impressions

    52 Retweets

    242 Likes

    95 Bookmarks

    0 Replies

    0 Quotes

  6. How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel’s SMB implementation – Sean Heelan's Blog https://t.co/bMdPz3FNgK

    @akaclandestine

    22 Aug 2025

    1511 Impressions

    6 Retweets

    25 Likes

    12 Bookmarks

    0 Replies

    0 Quotes

  7. Vulnerability research using LLMs (OpenAI’s o3): Zero day in Linux kernel’s SMB (CVE-2025-37899) https://t.co/1UdtbL2MhZ Credits @seanhn #infsec #llm https://t.co/XSFT3MEyIB

    @0xor0ne

    29 Jul 2025

    9983 Impressions

    59 Retweets

    278 Likes

    109 Bookmarks

    0 Replies

    1 Quote

  8. AI Finds CVE-2025-37899 Zero-Day In Linux SMB Kernel #CISO https://t.co/ywmEF3MdHW

    @compuchris

    25 Jul 2025

    17 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  9. o3 found CVE-2025-37899, a use-after-free vulnerability in Linux kernel's SMB implementation. This is test-time compute scaling in action. More runs -> higher coverage - in a bechmark run @seanhn found that o3 can find CVE-2025-37778 (kerberos auth vuln) in 8 of the 100 runs

    @phbenz

    4 Jul 2025

    32 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  10. 🔍 Using AI to Find a Linux Kernel Zero-Day Sean Heelan explains how he used OpenAI’s o3 model to uncover CVE-2025-37899. This is a remote zero-day vulnerability in the Linux kernel’s SMB implementation. He found the vulnerability using just the o3 API—no extra framewo

    @GotoNathan

    12 Jun 2025

    114 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  11. 🔍 Using AI to Find a Linux Kernel Zero-Day Sean Heelan explains how he used OpenAI’s o3 model to uncover CVE-2025-37899. This is a remote zero-day vulnerability in the Linux kernel’s SMB implementation. He found the vulnerability using just the o3 API—no extra framewo

    @GotoNathan

    12 Jun 2025

    116 Impressions

    0 Retweets

    1 Like

    1 Bookmark

    0 Replies

    0 Quotes

  12. 🔍 Using AI to Find a Linux Kernel Zero-Day Sean Heelan explains how he used OpenAI’s o3 model to uncover CVE-2025-37899. This is a remote zero-day vulnerability in the Linux kernel’s SMB implementation. He found the vulnerability using just the o3 API—no extra framewo

    @GotoNathan

    12 Jun 2025

    156 Impressions

    0 Retweets

    2 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  13. 🔍 Using AI to Find a Linux Kernel Zero-Day Sean Heelan explains how he used OpenAI’s o3 model to uncover CVE-2025-37899. This is a remote zero-day vulnerability in the Linux kernel’s SMB implementation. He found the vulnerability using just the o3 API—no extra framewo

    @GotoNathan

    12 Jun 2025

    116 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  14. LLM (OpenAI’s o3) for vulnerability research. Zero day in Linux kernel’s SMB (CVE-2025-37899) https://t.co/1UdtbL2MhZ Credits @seanhn #infsec #llm https://t.co/4Tsa3nFxLO

    @0xor0ne

    12 Jun 2025

    10416 Impressions

    60 Retweets

    227 Likes

    91 Bookmarks

    1 Reply

    0 Quotes

  15. #exploit 1. CVE-2025-32756: https://t.co/1w8oAjYxV0 Fortinet (FortiVoice, FortiMail, FortiNDR, FortiRecorder, FortiCamera) Stack-based BoF 2. CVE-2025-49223: https://t.co/0HK0aFCF70 Prototype Pollution in Billboard.js 3. CVE-2025-37899: https://t.co/RnMzAPQJjW Linux kernel SMB

    @ksg93rd

    8 Jun 2025

    1165 Impressions

    4 Retweets

    14 Likes

    9 Bookmarks

    1 Reply

    0 Quotes

  16. 🚩 AI Discovers Linux Kernel SMB Zero-Day Vulnerability CVE-2025-37899 https://t.co/cKh8aMKJ8A A critical use-after-free vulnerability (CVE-2025-37899) in the Linux kernel's ksmbd module was uncovered using OpenAI's o3 language model. The flaw arises when multiple threads

    @Huntio

    6 Jun 2025

    583 Impressions

    4 Retweets

    14 Likes

    2 Bookmarks

    0 Replies

    0 Quotes

  17. What if we could codify expert reasoning and scale it? @seanheelan’s latest work using the O3 reasoning model led to the discovery of CVE-2025-37899—a remote Linux kernel SMB zero-day. A standout example of intelligence amplification in action. https://t.co/sIdSOu6tBg https:

    @nuroshift

    6 Jun 2025

    39 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  18. Great example of the power of @OpenAI's o3 model. o3 spotted a CVE-2025-37899, a remote zero-day use-after-free bug in the Linux kernel’s SMB (ksmbd) implementation by reasoning across12,000 lines of code. ⚙️ The Core Concepts Use-after-free appears when freed memory is

    @rohanpaul_ai

    4 Jun 2025

    3709 Impressions

    6 Retweets

    24 Likes

    12 Bookmarks

    1 Reply

    0 Quotes

  19. How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel’s SMB implementation https://t.co/64aIViHRgW #security #cybersecurity

    @eyalestrin

    2 Jun 2025

    19 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  20. chatgpt нашел уязвимость в Linux, неделю назад ⚠️ Модель o3 OpenAI обнаружила уязвимость (CVE-2025-37899) в модуле ksmbd ядра Linux была, позволяющая выполнять код на уровне я

    @warnetik

    1 Jun 2025

    34 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  21. Believe it or not, #OpenAI's o3 just uncovered a remote 0-day in the #Linux #kernel's SMB code—CVE-2025-37899. A patch has already been rolled out. https://t.co/EfMN8eHpf5

    @linuxiac

    29 May 2025

    1406 Impressions

    16 Retweets

    64 Likes

    3 Bookmarks

    1 Reply

    1 Quote

  22. AI Discovers Zero-Day Vulnerability in Linux Kernel 🚨 OpenAI's o3 model just made cybersecurity history by discovering CVE-2025-37899 - a critical zero-day vulnerability buried deep in Linux kernel's SMB implementation. What makes this groundbreaking? ✅ o3 analyzed 12,000+

    @simbianai

    29 May 2025

    52 Impressions

    0 Retweets

    2 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  23. How OpenAI’s o3 Model was used to find zeroday Vulnerability in the Linux kernel (CVE-2025-37899 for the SMB implementation) - Blog post by Sean Heelan @seanhn #LLM #Cybersecurity https://t.co/hg0JHdzfGu

    @lcheylus

    28 May 2025

    146 Impressions

    2 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  24. Un chercheur en sécurité a identifié la vulnérabilité CVE-2025-37899 dans le noyau Linux grâce à l’IA. 👉 https://t.co/IDLQSMPp1L 👉 La CVE : https://t.co/Zo8VF9YzRi https://t.co/CH4Oe65poV

    @bearstech

    28 May 2025

    1626 Impressions

    5 Retweets

    18 Likes

    7 Bookmarks

    0 Replies

    0 Quotes

  25. La IA demuestra su potencial en #ciberseguridad: usando OpenAI, se descubrió la vulnerabilidad zero-day CVE-2025-37899 en la implementación SMB del kernel de Linux. Los modelos de lenguaje ya pueden identificar fallos complejos y acelerar este trabajo https://t.co/j90kOG49u7 h

    @henryraul

    28 May 2025

    220 Impressions

    11 Retweets

    7 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  26. o3によるCVE-2025-37899発見の解析と解説 https://t.co/DFzmxNbMpW

    @GithubMatome

    28 May 2025

    25 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  27. 🚨 OpenAI’s new o3 model just helped spot a zero-day Linux kernel bug (CVE-2025-37899) — no tools, just code + prompts. 🔍🐧 Researcher Sean Heelan used o3 to uncover a use-after-free vulnerability with kernel-level impact. AI + cybersecurity = real-world breakthrough

    @moaijobs

    27 May 2025

    55 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  28. ショーン・ヒーラン氏が「OpenAI o3」を使ってLinuxカーネルサーバー「ksmbd」のゼロデイ脆弱性を発見!正式に「CVE-2025-37899」として報告される https://t.co/IjK0IryqO4 @nikkeimatomeより

    @nikkeimatome

    27 May 2025

    66 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  29. Zero-day vulnerability in Linux kernel SMB discovered via ChatGPT CVE-2025-37899 #UPDATE https://t.co/6OOM0uVaGw

    @JadenJohnsNews

    26 May 2025

    6 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  30. Vulnerabilidad de día cero en SMB del kernel de Linux descubierta mediante ChatGPT CVE-2025-37899 https://t.co/9cRF5dUzW3 https://t.co/epjijWu26j

    @elhackernet

    26 May 2025

    20448 Impressions

    127 Retweets

    422 Likes

    109 Bookmarks

    4 Replies

    2 Quotes

  31. Using only OpenAI’s new o3 model, researcher Sean Heelan uncovered CVE-2025-37899 — a high-risk use-after-free flaw in the Linux kernel’s ksmbd module. The AI identified the bug without any extra tools, showcasing the power of LLMs in accelerating vulnerability research. ht

    @deeptechstars

    26 May 2025

    46 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  32. Artificial intelligence is helping with #cybersecurity How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel’s SMB implementation – Sean Heelan's Blog https://t.co/EM35479Ei9

    @MHiesboeck

    26 May 2025

    694 Impressions

    0 Retweets

    4 Likes

    1 Bookmark

    1 Reply

    0 Quotes

  33. OpenAI's o3 API Helps Find Linux Zero-Day Vulnerability A security researcher details how he used OpenAI's o3 API to find a zero-day vulnerability (CVE-2025-37899) in the Linux kernel's SMB implementation by analyzing code. #OpenAI #Security #Linux https://t.co/6PHf7Lw6ek

    @AI_Techie_Arun

    26 May 2025

    63 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  34. How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel's SMB implementation https://t.co/Mu2xcIgseB

    @TimCohn

    26 May 2025

    5 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  35. o3独立发现了Linux的0-day漏洞 (CVE-2025-37899) 看起来在量子计算实现之前,似乎只有实体资产和离线冷钱包是真正安全的资产,其他的数字和产权类资产都有重大风险。

    @iamai_eth

    25 May 2025

    1070 Impressions

    1 Retweet

    7 Likes

    2 Bookmarks

    0 Replies

    0 Quotes

  36. https://t.co/gx76MCZz2V - 使用OpenAI的o3模型找到Linux核心SMB實作的零日漏洞CVE-2025-37899。 - 該漏洞是SMB 'logoff'指令處理器中的Use-After-Free。 - o3成功分析並找出漏洞,展現其程式碼推理能力。 - o3也協助找到另一個相似的

    @Evan_Lin

    25 May 2025

    677 Impressions

    4 Retweets

    8 Likes

    1 Bookmark

    0 Replies

    1 Quote

  37. https://t.co/iGMVuOYh5e “How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel’s SMB implementation”

    @TheRealAdamG

    25 May 2025

    4468 Impressions

    5 Retweets

    89 Likes

    14 Bookmarks

    4 Replies

    0 Quotes

  38. How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel’s SMB implementation – Sean Heelan's Blog https://t.co/AeCCzfkZeH

    @rocky2rockz4

    25 May 2025

    27 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  39. #OpenAI's o3 model independently discovered a Linux kernel SMB zero-day vulnerability (CVE-2025-37899) 😱! No complex tools needed—just API code analysis, and its fix even outperformed humans 👏. A new era of AI security testing? https://t.co/j0Gqusj69w

    @dlimeng192048

    25 May 2025

    39 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  40. 最近独立研究员Seen Heelan用OpenAI的o3模型发现了Linux内核的远程零日漏洞CVE-2025-37899,还是首次由大语言模型独立发现的内核级漏洞 仅用o3的API,检查12000行代码100次就揪出了“释放后使用”漏洞,还能给出超棒的

    @daizhe9898

    25 May 2025

    63 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  41. この記事をおすすめしました "How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel’s SMB implementation" via @techfeedapp #techfeed https://t.co/elTLtQVUW9

    @yume_piece1010

    25 May 2025

    62 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  42. How I used o3 to find CVE-2025-37899, a remote zeroday vulnerability in the Linux kernel’s SMB implementation https://t.co/FyrGqQiiln

    @yousukezan

    25 May 2025

    2528 Impressions

    1 Retweet

    13 Likes

    8 Bookmarks

    0 Replies

    0 Quotes

  43. CVE-2025-37899 revealed via O3: a significant Linux kernel SMB RCE. Real-world impact underscores O3's capability in automating complex vulnerability discovery. Expect higher scrutiny on kernel security while automated tools gain credibility. https://t.co/zX7wgRAZLv

    @0xOnlyCalls

    25 May 2025

    125 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  44. Security researcher Sean Heelan used OpenAI’s o3 model to discover a critical zero-day (CVE-2025-37899) in the Linux kernel’s SMB server. o3 flagged a race condition leading to a use-after-free bug showing how AI can now spot real, complex vulns in kernel code.

    @sharathnryn

    25 May 2025

    53 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  45. Security researcher Sean Heelan used OpenAI’s o3 model to discover a critical zero-day (CVE-2025-37899) in the Linux kernel’s SMB server. o3 flagged a race condition leading to a use-after-free bug — showing how AI can now spot real, complex vulns in kernel code.

    @sharathnryn

    25 May 2025

    8 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  46. OPENAI’S O3 UNCOVERS LINUX ZERO-DAY FLAW! A researcher used OpenAI’s o3 model to discover CVE-2025-37899, a critical remote zero-day vulnerability in the Linux kernel’s SMB, showcasing AI’s power in cybersecurity. #AI https://t.co/s0c0fXtvXT

    @ai_24x7

    25 May 2025

    52 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  47. 【ニュース速報:Tech blogs】2025-05-25 1. 私がo3を使用して、LinuxカーネルのSMB実装におけるリモートゼロデイ脆弱性CVE-2025-37899を発見した方法について説明します。 https://t.co/ndzCPyRE1X 2. f2 https://t.co/qLxDZkcxzb #T

    @Masato1864646

    25 May 2025

    41 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  48. LinuxカーネルのSMB実装にゼロデイ脆弱性(CVE-2025-37899)が発見されたんだけど、実はOpenAIのLLM「o3」が見つけたんだよ。AIが並列処理の危険なバグを人間より先に発見したってことで、セキュリティ分野に衝撃

    @techandeco4242

    25 May 2025

    82 Impressions

    1 Retweet

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  49. Linux kernel vulnerability found using o3. The vulnerability CVE-2025-37899, a use-after-free in the handler for the SMB ‘logoff’ command was found by training o3. Understanding the vulnerability requires reasoning about concurrent connections to the server, and how they may

    @mukulneetika

    25 May 2025

    450 Impressions

    0 Retweets

    2 Likes

    0 Bookmarks

    0 Replies

    1 Quote

  50. 【ニュース速報:Tech blogs】2025-05-25 1. 私がo3を使用して、LinuxカーネルのSMB実装におけるリモートゼロデイ脆弱性CVE-2025-37899を見つけた方法について説明します。 https://t.co/ndzCPyRE1X 2. f2 https://t.co/qLxDZkcxzb #T

    @Masato1864646

    25 May 2025

    40 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

  1. In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level When recovering hugepages in the shadow MMU, verify that the base gfn of the shadow page is actually contained within the target memslot, *before* querying the max mapping level given the shadow page's gfn. Failure to pre-check the validity of the gfn can lead to an out-of-bounds access to the slot's lpage_info (which typically manifests as a host #PF because the lpage_info is vmalloc'd) if the guest creates a hugepage mapping (in its PTEs) that extends "below" the bounds of a memslot. When faulting in memory for a guest, and the size of the guest mapping is greater than KVM's (current) max mapping, then KVM will create a "direct" shadow page (direct in that there are no gPTEs to shadow, and so the target gfn is a direct calculation given the base gfn of the shadow page). The hugepage recovery flow looks for such direct shadow pages, as forcing 4KiB mappings when dirty logging generates the guest > host mapping size case. When the 4KiB restriction is lifted, then KVM can replace the shadow page with a hugepage. But if KVM originally used a smaller mapping than the guest because the range of memory covered by the guest hugepage exceeds the bounds of a memslot, then KVM will link a direct shadow page with a gfn that is outside the bounds of the memslot being used to fault in memory. The rmap entry added for the leaf mapping is correct and within bounds, but the gfn of the leaf SPTE's parent shadow page will be out of bounds. BUG: unable to handle page fault for address: ffffc90000806ffc #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 100000067 P4D 100000067 PUD 1002a7067 PMD 10612f067 PTE 0 Oops: Oops: 0000 [#1] SMP CPU: 13 UID: 1000 PID: 757 Comm: mmu_stress_test Not tainted 7.1.0-rc1-48ce1e26eace-x86_pir_to_irr_comments-vm #341 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:kvm_mmu_max_mapping_level+0x79/0x2b0 [kvm] Call Trace: <TASK> kvm_mmu_recover_huge_pages+0x21b/0x320 [kvm] kvm_set_memslot+0x1ee/0x590 [kvm] kvm_set_memory_region.part.0+0x3a1/0x4d0 [kvm] kvm_vm_ioctl+0x9bf/0x15d0 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb7/0xbb0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f21c0f1a9bf </TASK> Don't bother pre-checking the bounds of the potential hugepage, i.e. don't check that e.g. sp->gfn + KVM_PAGES_PER_HPAGE(sp->role.level + 1) is also within the memslot, as the checks performed by kvm_mmu_max_mapping_level() are a superset of the basic bounds checks. I.e. pre-checking the full range would be a dubious micro-optimization.CVE-2026-63807
  2. In the Linux kernel, the following vulnerability has been resolved: KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() Drop a BUG_ON() that has been reachable since it was first added, way back in 2009, and instead use get_unaligned() to perform potentially-unaligned accesses. For a given store, KVM x86's emulator tracks the entire value in the destination operand, x86_emulate_ctxt.dst. If the destination is memory, and the target splits multiple pages and/or is emulated MMIO, then KVM handles each fragment independently. E.g. on a page split starting at page offset 0xffc, KVM writes 4 bytes to the first page, then the remaining bytes to the second page, using ctxt->dst as the source for both (with appropriate offsets). If the destination splits a page *and* hits emulated MMIO on the second page, then KVM will complete the write to the first page, then emulate the MMIO access to the second page. If there is a datamatch-enabled ioeventfd at offset 0 of the second page, then KVM will process the remainder of the store as a potential ioeventfd signal. Putting it all together, if the guest emits a store that splits a page starting at page offset N, and the second page has a datamatch-enabled ioeventfd at offset 0, then KVM will check for datamatch using &dst.valptr[N] as the source. Due to dst (and thus dst.valptr) being 32-byte aligned, if N is not aligned to @len, the BUG_ON() fires. E.g. with a 16-byte store at page offset 0xffc, to an ioeventfd of len 8, all initial checks in ioeventfd_in_range() will succeed, and the BUG_ON() fires due to @val being 4-byte aligned, but not 8-byte aligned. ------------[ cut here ]------------ kernel BUG at arch/x86/kvm/../../../virt/kvm/eventfd.c:783! Oops: invalid opcode: 0000 [#1] SMP CPU: 0 UID: 1000 PID: 615 Comm: repro Not tainted 7.1.0-rc2-ff238429d1ea #365 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:ioeventfd_write+0x6c/0x70 [kvm] Call Trace: <TASK> __kvm_io_bus_write+0x85/0xb0 [kvm] kvm_io_bus_write+0x53/0x80 [kvm] vcpu_mmio_write+0x66/0xf0 [kvm] emulator_read_write_onepage+0x12a/0x540 [kvm] emulator_read_write+0x109/0x2b0 [kvm] x86_emulate_insn+0x4f8/0xfb0 [kvm] x86_emulate_instruction+0x181/0x790 [kvm] kvm_mmu_page_fault+0x313/0x630 [kvm] vmx_handle_exit+0x18a/0x590 [kvm_intel] kvm_arch_vcpu_ioctl_run+0xc81/0x1c90 [kvm] kvm_vcpu_ioctl+0x2d5/0x970 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb7/0x890 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f19c931a9bf </TASK> Modules linked in: kvm_intel kvm irqbypass ---[ end trace 0000000000000000 ]--- In a perfect world, the fix would be to simply delete the BUG_ON(), as KVM x86 doesn't perform alignment checks on "normal" memory accesses at CPL0. Sadly, C99 ruins all the fun; while the x86 architecture plays nice, dereferencing an unaligned pointer directly is undefined behavior in C, e.g. triggers splats when running with CONFIG_UBSAN_ALIGNMENT=y.CVE-2026-63806
  3. In the Linux kernel, the following vulnerability has been resolved: hdlc_ppp: sync per-proto timers before freeing hdlc state Each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp registers a timer via timer_setup(). That struct ppp is the hdlc->state allocation, which detach_hdlc_protocol() frees with kfree() in both teardown paths: unregister_hdlc_device() and the re-attach inside attach_hdlc_protocol(). The ppp proto never registered a .detach callback, so detach_hdlc_protocol() performs no timer synchronization before the kfree(). The only cancel, timer_delete(&proto->timer) in ppp_cp_event(), is partial (it does not wait for a running callback) and only runs on the ->CLOSED transition; ppp_stop()/ppp_close() do not sync either. A ppp_timer callback already executing (blocked on ppp->lock) survives the kfree and then dereferences proto->state / ppp->lock in freed memory, leading to a use-after-free. Fix this by adding a .detach helper that calls timer_shutdown_sync() on every per-proto timer. detach_hdlc_protocol() invokes proto->detach(dev) before kfree(hdlc->state), so timer_shutdown_sync() now runs on both free paths. timer_shutdown_sync() is used instead of timer_delete_sync() because the keepalive path re-arms the timer through add_timer()/mod_timer() and shutdown blocks any re-activation during teardown. Initialize the per-protocol timers in ppp_ioctl() when the protocol is attached, and remove the now-redundant timer_setup() from ppp_start(), so that the timers are initialized exactly once at attach time and ppp_timer_release() never operates on uninitialized timer_list structures. attach_hdlc_protocol() uses kmalloc() (not kzalloc), so struct ppp's protos[i].timer is uninitialized garbage until the first timer_setup(); without this init-at-attach, attaching the PPP protocol without ever bringing the device up would leave timer_shutdown_sync() operating on uninitialized memory in .detach. Moving the init out of ppp_start() (which only runs on NETDEV_UP) into the attach path makes the initialization unconditional and avoids initializing the same timer_list twice. This bug was found by static analysis.CVE-2026-63803