CVE-2024-39488

一、漏洞信息
 漏洞编号：[CVE-2024-39488](https://nvd.nist.gov/vuln/detail/CVE-2024-39488)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0
 CVSS V2.0分值：
  BaseScore：0.0 Medium
  Vector：CVSS：2.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRYWhen CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytesto bug_table entries, and as a result the last entry in a bug table willbe ignored, potentially leading to an unexpected panic(). All priorentries in the table will be handled correctly.The arm64 ABI requires that struct fields of up to 8 bytes arenaturally-aligned, with padding added within a struct such that structare suitably aligned within arrays.When CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:	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	}... with 12 bytes total, requiring 4-byte alignment.When CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:	struct bug_entry {		signed int      bug_addr_disp;	// 4 bytes		unsigned short  flags;		// 2 bytes		< implicit padding >		// 2 bytes	}... with 8 bytes total, with 6 bytes of data and 2 bytes of trailingpadding, requiring 4-byte alginment.When we create a bug_entry in assembly, we align the start of the entryto 4 bytes, which implicitly handles padding for any prior entries.However, we do not align the end of the entry, and so whenCONFIG_DEBUG_BUGVERBOSE=n, the final entry lacks the trailing paddingbytes.For the main kernel image this is not a problem as find_bug() doesn tdepend on the trailing padding bytes when searching for entries:	for (bug = __start___bug_table; bug < __stop___bug_table; ++bug)		if (bugaddr == bug_addr(bug))			return bug;However for modules, module_bug_finalize() depends on the trailingbytes when calculating the number of entries:	mod->num_bugs = sechdrs[i].sh_size / sizeof(struct bug_entry);... and as the last bug_entry lacks the necessary padding bytes, this entrywill not be counted, e.g. in the case of a single entry:	sechdrs[i].sh_size == 6	sizeof(struct bug_entry) == 8;	sechdrs[i].sh_size / sizeof(struct bug_entry) == 0;Consequently module_find_bug() will miss the last bug_entry when it does:	for (i = 0; i < mod->num_bugs; ++i, ++bug)		if (bugaddr == bug_addr(bug))			goto out;... which can lead to a kenrel panic due to an unhandled bug.This can be demonstrated with the following module:	static int __init buginit(void)	{		WARN(1,  hello n );		return 0;	}	static void __exit bugexit(void)	{	}	module_init(buginit);	module_exit(bugexit);	MODULE_LICENSE( GPL );... which will trigger a kernel panic when loaded:	------------[ cut here ]------------	hello	Unexpected kernel BRK exception at EL1	Internal error: BRK handler: 00000000f2000800 [#1] PREEMPT SMP	Modules linked in: hello(O+)	CPU: 0 PID: 50 Comm: insmod Tainted: G           O       6.9.1 #8	Hardware name: linux,dummy-virt (DT)	pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)	pc : buginit+0x18/0x1000 [hello]	lr : buginit+0x18/0x1000 [hello]	sp : ffff800080533ae0	x29: ffff800080533ae0 x28: 0000000000000000 x27: 0000000000000000	x26: ffffaba8c4e70510 x25: ffff800080533c30 x24: ffffaba8c4a28a58	x23: 0000000000000000 x22: 0000000000000000 x21: ffff3947c0eab3c0	x20: ffffaba8c4e3f000 x19: ffffaba846464000 x18: 0000000000000006	x17: 0000000000000000 x16: ffffaba8c2492834 x15: 0720072007200720	x14: 0720072007200720 x13: ffffaba8c49b27c8 x12: 0000000000000312	x11: 0000000000000106 x10: ffffaba8c4a0a7c8 x9 : ffffaba8c49b27c8	x8 : 00000000ffffefff x7 : ffffaba8c4a0a7c8 x6 : 80000000fffff000	x5 : 0000000000000107 x4 : 0000000000000000 x3 : 0000000000000000	x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff3947c0eab3c0	Call trace:	 buginit+0x18/0x1000 [hello]	 do_one_initcall+0x80/0x1c8	 do_init_module+0x60/0x218	 load_module+0x1ba4/0x1d70	 __do_sys_init_module+0x198/0x1d0	 __arm64_sys_init_module+0x1c/0x28	 invoke_syscall+0x48/0x114	 el0_svc---truncated---
 漏洞公开时间：2024-07-10 16:15:11
 漏洞创建时间：2024-07-11 05:03:20
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-39488
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/22469a0335a1a1a690349b58bcb55822457df81e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3fd487ffaa697ddb05af78a75aaaddabe71c52b0 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/461a760d578b2b2c2faac3040b6b7c77baf128f8 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/9f2ad88f9b349554f64e4037ec185c84d7dd9c7d |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c1929c041a262a4a27265db8dce3619c92aa678c |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c27a2f7668e215c1ebbccd96fab27a220a93f1f7 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f221bd58db0f6ca087ac0392284f6bce21f4f8ea |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ffbf4fb9b5c12ff878a10ea17997147ea4ebea6f |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-39488 | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-39488.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/stable/c/f221bd58db0f6ca087ac0392284f6bce21f4f8ea | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/stable/c/22469a0335a1a1a690349b58bcb55822457df81e | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/stable/c/461a760d578b2b2c2faac3040b6b7c77baf128f8 | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/stable/c/c1929c041a262a4a27265db8dce3619c92aa678c | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/stable/c/3fd487ffaa697ddb05af78a75aaaddabe71c52b0 | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/stable/c/9f2ad88f9b349554f64e4037ec185c84d7dd9c7d | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/stable/c/c27a2f7668e215c1ebbccd96fab27a220a93f1f7 | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://git.kernel.org/stable/c/ffbf4fb9b5c12ff878a10ea17997147ea4ebea6f | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-39488 | https://bugzilla.suse.com/show_bug.cgi?id=1227618 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-39488 |
| cve_search |  | https://git.kernel.org/stable/c/f221bd58db0f6ca087ac0392284f6bce21f4f8ea |
| cve_search |  | https://git.kernel.org/stable/c/22469a0335a1a1a690349b58bcb55822457df81e |
| cve_search |  | https://git.kernel.org/stable/c/461a760d578b2b2c2faac3040b6b7c77baf128f8 |
| cve_search |  | https://git.kernel.org/stable/c/c1929c041a262a4a27265db8dce3619c92aa678c |
| cve_search |  | https://git.kernel.org/stable/c/3fd487ffaa697ddb05af78a75aaaddabe71c52b0 |
| cve_search |  | https://git.kernel.org/stable/c/9f2ad88f9b349554f64e4037ec185c84d7dd9c7d |
| cve_search |  | https://git.kernel.org/stable/c/c27a2f7668e215c1ebbccd96fab27a220a93f1f7 |
| cve_search |  | https://git.kernel.org/stable/c/ffbf4fb9b5c12ff878a10ea17997147ea4ebea6f |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-39488 | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/linus/ffbf4fb9b5c12ff878a10ea17997147ea4ebea6f (6.10-rc1) | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/stable/c/f221bd58db0f6ca087ac0392284f6bce21f4f8ea | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/stable/c/22469a0335a1a1a690349b58bcb55822457df81e | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/stable/c/461a760d578b2b2c2faac3040b6b7c77baf128f8 | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/stable/c/c1929c041a262a4a27265db8dce3619c92aa678c | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/stable/c/3fd487ffaa697ddb05af78a75aaaddabe71c52b0 | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/stable/c/9f2ad88f9b349554f64e4037ec185c84d7dd9c7d | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/stable/c/c27a2f7668e215c1ebbccd96fab27a220a93f1f7 | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://git.kernel.org/stable/c/ffbf4fb9b5c12ff878a10ea17997147ea4ebea6f | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-39488 | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-39488 | https://ubuntu.com/security/CVE-2024-39488 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-39488 | https://ubuntu.com/security/CVE-2024-39488 |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux |  | https://git.kernel.org/linus/ffbf4fb9b5c12ff878a10ea17997147ea4ebea6f | https://git.kernel.org/linus/9fb7410f955f7a62c1f882ca8f9ffd4525907e28 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
    In the Linux kernel, the following vulnerability has been resolved:arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRYWhen CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytesto bug_table entries, and as a result the last entry in a bug table willbe ignored, potentially leading to an unexpected panic(). All priorentries in the table will be handled correctly.The arm64 ABI requires that struct fields of up to 8 bytes arenaturally-aligned, with padding added within a struct such that structare suitably aligned within arrays.When CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:struct bug_entry {signed int      bug_addr_disp;// 4 bytessigned int      file_disp;// 4 bytesunsigned short  line;// 2 bytesunsigned short  flags;// 2 bytes}... with 12 bytes total, requiring 4-byte alignment.When CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:struct bug_entry {signed int      bug_addr_disp;// 4 bytesunsigned short  flags;// 2 bytes&lt; implicit padding &gt;// 2 bytes}... with 8 bytes total, with 6 bytes of data and 2 bytes of trailingpadding, requiring 4-byte alginment.When we create a bug_entry in assembly, we align the start of the entryto 4 bytes, which implicitly handles padding for any prior entries.However, we do not align the end of the entry, and so whenCONFIG_DEBUG_BUGVERBOSE=n, the final entry lacks the trailing paddingbytes.For the main kernel image this is not a problem as find_bug() doesn&#39;tdepend on the trailing padding bytes when searching for entries:for (bug = __start___bug_table; bug &lt; __stop___bug_table; ++bug)if (bugaddr == bug_addr(bug))return bug;However for modules, module_bug_finalize() depends on the trailingbytes when calculating the number of entries:mod-&gt;num_bugs = sechdrs[i].sh_size / sizeof(struct bug_entry);... and as the last bug_entry lacks the necessary padding bytes, this entrywill not be counted, e.g. in the case of a single entry:sechdrs[i].sh_size == 6sizeof(struct bug_entry) == 8;sechdrs[i].sh_size / sizeof(struct bug_entry) == 0;Consequently module_find_bug() will miss the last bug_entry when it does:for (i = 0; i &lt; mod-&gt;num_bugs; ++i, ++bug)if (bugaddr == bug_addr(bug))goto out;... which can lead to a kenrel panic due to an unhandled bug.This can be demonstrated with the following module:static int __init buginit(void){WARN(1, &#34;hello n&#34;);return 0;}static void __exit bugexit(void){}module_init(buginit);module_exit(bugexit);MODULE_LICENSE(&#34;GPL&#34;);... which will trigger a kernel panic when loaded:------------[ cut here ]------------helloUnexpected kernel BRK exception at EL1Internal error: BRK handler: 00000000f2000800 [#1] PREEMPT SMPModules linked in: hello(O+)CPU: 0 PID: 50 Comm: insmod Tainted: G           O       6.9.1 #8Hardware name: linux,dummy-virt (DT)pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)pc : buginit+0x18/0x1000 [hello]lr : buginit+0x18/0x1000 [hello]sp : ffff800080533ae0x29: ffff800080533ae0 x28: 0000000000000000 x27: 0000000000000000x26: ffffaba8c4e70510 x25: ffff800080533c30 x24: ffffaba8c4a28a58x23: 0000000000000000 x22: 0000000000000000 x21: ffff3947c0eab3c0x20: ffffaba8c4e3f000 x19: ffffaba846464000 x18: 0000000000000006x17: 0000000000000000 x16: ffffaba8c2492834 x15: 0720072007200720x14: 0720072007200720 x13: ffffaba8c49b27c8 x12: 0000000000000312x11: 0000000000000106 x10: ffffaba8c4a0a7c8 x9 : ffffaba8c49b27c8x8 : 00000000ffffefff x7 : ffffaba8c4a0a7c8 x6 : 80000000fffff000x5 : 0000000000000107 x4 : 0000000000000000 x3 : 0000000000000000x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff3947c0eab3c0Call trace: buginit+0x18/0x1000 [hello] do_one_initcall+0x80/0x1c8 do_init_module+0x60/0x218 load_module+0x1ba4/0x1d70 __do_sys_init_module+0x198/0x1d0 __arm64_sys_init_module+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x34/0xd8 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x190/0x194Code: d0ffffe0 910003fd 91000000 9400000b (d4210000)---[ end trace 0000000000000000 ]---Kernel panic - not syncing: BRK handler: Fatal exceptionFix thi
 openEuler评分：
  5.5
 Vector：CVSS：2.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP1(5.10.0):受影响
3.openEuler-22.03-LTS-SP3(5.10.0):受影响
4.openEuler-24.03-LTS(6.6.0):受影响
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响
6.master(6.1.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP1(5.10.0):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.master(6.1.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-22.03-LTS-SP4(5.10.0):否

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-1863

src-openEuler/kernel

内容风险标识

评论 (23)

src-openEuler/kernel .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2024-39488

评论 (23)

搜索帮助

src-openEuler/kernel