Bug 1226834 (CVE-2024-36288)

Summary:	VUL-0: CVE-2024-36288: kernel: SUNRPC: Fix loop termination condition in gss_free_in_token_pages()
Product:	[Novell Products] SUSE Security Incidents	Reporter:	SMASH SMASH <smash_bz>
Component:	Incidents	Assignee:	Security Team bot <security-team>
Status:	RESOLVED FIXED	QA Contact:	Security Team bot <security-team>
Severity:	Normal
Priority:	P3 - Medium	CC:	abergmann, mhocko
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
URL:	https://smash.suse.de/issue/411778/
Whiteboard:	CVSSv3.1:SUSE:CVE-2024-36288:5.5:(AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Found By:	Security Response Team	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description SMASH SMASH 2024-06-24 06:13:36 UTC

In the Linux kernel, the following vulnerability has been resolved:

SUNRPC: Fix loop termination condition in gss_free_in_token_pages()

The in_token->pages[] array is not NULL terminated. This results in
the following KASAN splat:

  KASAN: maybe wild-memory-access in range [0x04a2013400000008-0x04a201340000000f]

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-36288
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-36288.mbox
https://git.kernel.org/stable/c/57ff6c0a175930856213b2aa39f8c845a53e5b1c
https://git.kernel.org/stable/c/6ed45d20d30005bed94c8c527ce51d5ad8121018
https://git.kernel.org/stable/c/4cefcd0af7458bdeff56a9d8dfc6868ce23d128a
https://git.kernel.org/stable/c/b4878ea99f2b40ef1925720b1b4ca7f4af1ba785
https://git.kernel.org/stable/c/f9977e4e0cd98a5f06f2492b4f3547db58deabf5
https://git.kernel.org/stable/c/af628d43a822b78ad8d4a58d8259f8bf8bc71115
https://git.kernel.org/stable/c/0a1cb0c6102bb4fd310243588d39461da49497ad
https://git.kernel.org/stable/c/4a77c3dead97339478c7422eb07bf4bf63577008
https://www.cve.org/CVERecord?id=CVE-2024-36288
https://bugzilla.redhat.com/show_bug.cgi?id=2293645

Comment 1 Alexander Bergmann 2024-06-24 06:42:09 UTC

Affected and fixed versions
===========================
Issue introduced in 6.9.3 with commit 8ca148915670 and fixed in 6.9.4 with commit 0a1cb0c6102b
Issue introduced in 6.10-rc1 with commit bafa6b4d95d9 and fixed in 6.10-rc3 with commit 4a77c3dead97
Issue introduced in 6.8.12 with commit a3c1afd5d7ad


None of SLE kernels are affected.

Comment 3 Andrea Mattiazzo 2024-07-01 13:37:40 UTC

All done, closing.