<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 03:30:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68198 — crash: fix crashkernel resource shrink</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68198</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crash: fix crashkernel resource shrink&lt;/p&gt;
&lt;p&gt;When crashkernel is configured with a high reservation, shrinking its
value below the low crashkernel reservation causes two issues:&lt;/p&gt;
&lt;p&gt;1. Invalid crashkernel resource objects
2. Kernel crash if crashkernel shrinking is done twice&lt;/p&gt;
&lt;p&gt;For example, with crashkernel=200M,high, the kernel reserves 200MB of high
memory and some default low memory (say 256MB).  The reservation appears
as:&lt;/p&gt;
&lt;p&gt;cat /proc/iomem | grep -i crash
af000000-beffffff : Crash kernel
433000000-43f7fffff : Crash kernel&lt;/p&gt;
&lt;p&gt;If crashkernel is then shrunk to 50MB (echo 52428800 &amp;gt;
/sys/kernel/kexec_crash_size), /proc/iomem still shows 256MB reserved:
af000000-beffffff : Crash kernel&lt;/p&gt;
&lt;p&gt;Instead, it should show 50MB:
af000000-b21fffff : Crash kernel&lt;/p&gt;
&lt;p&gt;Further shrinking crashkernel to 40MB causes a kernel crash with the
following trace (x86):&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000038
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
&amp;lt;snip...&amp;gt;
Call Trace: &amp;lt;TASK&amp;gt;
? __die_body.cold+0x19/0x27
? page_fault_oops+0x15a/0x2f0
? search_module_extables+0x19/0x60
? search_bpf_extables+0x5f/0x80
? exc_page_fault+0x7e/0x180
? asm_exc_page_fault+0x26/0x30
? __release_resource+0xd/0xb0
release_resource+0x26/0x40
__crash_shrink_memory+0xe5/0x110
crash_shrink_memory+0x12a/0x190
kexec_crash_size_store+0x41/0x80
kernfs_fop_write_iter+0x141/0x1f0
vfs_write+0x294/0x460
ksys_write+0x6d/0xf0
&amp;lt;snip...&amp;gt;&lt;/p&gt;
&lt;p&gt;This happens because __…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crash: fix crashkernel resource shrink&lt;/p&gt;
&lt;p&gt;When crashkernel is configured with a high reservation, shrinking its
value below the low crashkernel reservation causes two issues:&lt;/p&gt;
&lt;p&gt;1. Invalid crashkernel resource objects
2. Kernel crash if crashkernel shrinking is done twice&lt;/p&gt;
&lt;p&gt;For example, with crashkernel=200M,high, the kernel reserves 200MB of high
memory and some default low memory (say 256MB).  The reservation appears
as:&lt;/p&gt;
&lt;p&gt;cat /proc/iomem | grep -i crash
af000000-beffffff : Crash kernel
433000000-43f7fffff : Crash kernel&lt;/p&gt;
&lt;p&gt;If crashkernel is then shrunk to 50MB (echo 52428800 &amp;gt;
/sys/kernel/kexec_crash_size), /proc/iomem still shows 256MB reserved:
af000000-beffffff : Crash kernel&lt;/p&gt;
&lt;p&gt;Instead, it should show 50MB:
af000000-b21fffff : Crash kernel&lt;/p&gt;
&lt;p&gt;Further shrinking crashkernel to 40MB causes a kernel crash with the
following trace (x86):&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000038
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
&amp;lt;snip...&amp;gt;
Call Trace: &amp;lt;TASK&amp;gt;
? __die_body.cold+0x19/0x27
? page_fault_oops+0x15a/0x2f0
? search_module_extables+0x19/0x60
? search_bpf_extables+0x5f/0x80
? exc_page_fault+0x7e/0x180
? asm_exc_page_fault+0x26/0x30
? __release_resource+0xd/0xb0
release_resource+0x26/0x40
__crash_shrink_memory+0xe5/0x110
crash_shrink_memory+0x12a/0x190
kexec_crash_size_store+0x41/0x80
kernfs_fop_write_iter+0x141/0x1f0
vfs_write+0x294/0x460
ksys_write+0x6d/0xf0
&amp;lt;snip...&amp;gt;&lt;/p&gt;
&lt;p&gt;This happens because __…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68198</guid>
    </item>
  </channel>
</rss>
