<?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>Fri, 02 Oct 2026 18:39:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-39488 — arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-39488</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;arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY&lt;/p&gt;
&lt;p&gt;When CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytes
to bug_table entries, and as a result the last entry in a bug table will
be ignored, potentially leading to an unexpected panic(). All prior
entries in the table will be handled correctly.&lt;/p&gt;
&lt;p&gt;The arm64 ABI requires that struct fields of up to 8 bytes are
naturally-aligned, with padding added within a struct such that struct
are suitably aligned within arrays.&lt;/p&gt;
&lt;p&gt;When CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:&lt;/p&gt;
&lt;p&gt;struct bug_entry {
		signed int      bug_addr_disp;	// 4 bytes
		signed int      file_disp;	// 4 bytes
		unsigned short  line;		// 2 bytes
		unsigned short  flags;		// 2 bytes
	}&lt;/p&gt;
&lt;p&gt;... with 12 bytes total, requiring 4-byte alignment.&lt;/p&gt;
&lt;p&gt;When CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:&lt;/p&gt;
&lt;p&gt;struct bug_entry {
		signed int      bug_addr_disp;	// 4 bytes
		unsigned short  flags;		// 2 bytes
		&amp;lt; implicit padding &amp;gt;		// 2 bytes
	}&lt;/p&gt;
&lt;p&gt;... with 8 bytes total, with 6 bytes of data and 2 bytes of trailing
padding, requiring 4-byte alginment.&lt;/p&gt;
&lt;p&gt;When we create a bug_entry in assembly, we align the start of the entry
to 4 bytes, which implicitly handles padding for any prior entries.
However, we do not align the end of the entry, and so when
CONFIG_DEBUG_BUGVERBOSE=n, the final entry lacks the trailing padding
bytes.&lt;/p&gt;
&lt;p&gt;For the main kernel image this is not a problem as find_b…&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;arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY&lt;/p&gt;
&lt;p&gt;When CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytes
to bug_table entries, and as a result the last entry in a bug table will
be ignored, potentially leading to an unexpected panic(). All prior
entries in the table will be handled correctly.&lt;/p&gt;
&lt;p&gt;The arm64 ABI requires that struct fields of up to 8 bytes are
naturally-aligned, with padding added within a struct such that struct
are suitably aligned within arrays.&lt;/p&gt;
&lt;p&gt;When CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:&lt;/p&gt;
&lt;p&gt;struct bug_entry {
		signed int      bug_addr_disp;	// 4 bytes
		signed int      file_disp;	// 4 bytes
		unsigned short  line;		// 2 bytes
		unsigned short  flags;		// 2 bytes
	}&lt;/p&gt;
&lt;p&gt;... with 12 bytes total, requiring 4-byte alignment.&lt;/p&gt;
&lt;p&gt;When CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:&lt;/p&gt;
&lt;p&gt;struct bug_entry {
		signed int      bug_addr_disp;	// 4 bytes
		unsigned short  flags;		// 2 bytes
		&amp;lt; implicit padding &amp;gt;		// 2 bytes
	}&lt;/p&gt;
&lt;p&gt;... with 8 bytes total, with 6 bytes of data and 2 bytes of trailing
padding, requiring 4-byte alginment.&lt;/p&gt;
&lt;p&gt;When we create a bug_entry in assembly, we align the start of the entry
to 4 bytes, which implicitly handles padding for any prior entries.
However, we do not align the end of the entry, and so when
CONFIG_DEBUG_BUGVERBOSE=n, the final entry lacks the trailing padding
bytes.&lt;/p&gt;
&lt;p&gt;For the main kernel image this is not a problem as find_b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-39488</guid>
    </item>
  </channel>
</rss>
