552 lines
25 KiB
XML
552 lines
25 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<cvrfdoc xmlns="http://www.icasi.org/CVRF/schema/cvrf/1.1" xmlns:cvrf="http://www.icasi.org/CVRF/schema/cvrf/1.1">
|
|
<DocumentTitle xml:lang="en">An update for kernel is now available for openEuler-22.03-LTS</DocumentTitle>
|
|
<DocumentType>Security Advisory</DocumentType>
|
|
<DocumentPublisher Type="Vendor">
|
|
<ContactDetails>openeuler-security@openeuler.org</ContactDetails>
|
|
<IssuingAuthority>openEuler security committee</IssuingAuthority>
|
|
</DocumentPublisher>
|
|
<DocumentTracking>
|
|
<Identification>
|
|
<ID>openEuler-SA-2024-1283</ID>
|
|
</Identification>
|
|
<Status>Final</Status>
|
|
<Version>1.0</Version>
|
|
<RevisionHistory>
|
|
<Revision>
|
|
<Number>1.0</Number>
|
|
<Date>2024-03-15</Date>
|
|
<Description>Initial</Description>
|
|
</Revision>
|
|
</RevisionHistory>
|
|
<InitialReleaseDate>2024-03-15</InitialReleaseDate>
|
|
<CurrentReleaseDate>2024-03-15</CurrentReleaseDate>
|
|
<Generator>
|
|
<Engine>openEuler SA Tool V1.0</Engine>
|
|
<Date>2024-03-15</Date>
|
|
</Generator>
|
|
</DocumentTracking>
|
|
<DocumentNotes>
|
|
<Note Title="Synopsis" Type="General" Ordinal="1" xml:lang="en">kernel security update</Note>
|
|
<Note Title="Summary" Type="General" Ordinal="2" xml:lang="en">An update for kernel is now available for openEuler-22.03-LTS.</Note>
|
|
<Note Title="Description" Type="General" Ordinal="3" xml:lang="en">The Linux Kernel, the operating system core itself.
|
|
|
|
Security Fix(es):
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
f2fs: explicitly null-terminate the xattr list
|
|
|
|
When setting an xattr, explicitly null-terminate the xattr list. This
|
|
eliminates the fragile assumption that the unused xattr space is always
|
|
zeroed.(CVE-2023-52436)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
binder: fix use-after-free in shinker's callback
|
|
|
|
The mmap read lock is used during the shrinker's callback, which means
|
|
that using alloc->vma pointer isn't safe as it can race with munmap().
|
|
As of commit dd2283f2605e ("mm: mmap: zap pages with read mmap_sem in
|
|
munmap") the mmap lock is downgraded after the vma has been isolated.
|
|
|
|
I was able to reproduce this issue by manually adding some delays and
|
|
triggering page reclaiming through the shrinker's debug sysfs. The
|
|
following KASAN report confirms the UAF:
|
|
|
|
==================================================================
|
|
BUG: KASAN: slab-use-after-free in zap_page_range_single+0x470/0x4b8
|
|
Read of size 8 at addr ffff356ed50e50f0 by task bash/478
|
|
|
|
CPU: 1 PID: 478 Comm: bash Not tainted 6.6.0-rc5-00055-g1c8b86a3799f-dirty #70
|
|
Hardware name: linux,dummy-virt (DT)
|
|
Call trace:
|
|
zap_page_range_single+0x470/0x4b8
|
|
binder_alloc_free_page+0x608/0xadc
|
|
__list_lru_walk_one+0x130/0x3b0
|
|
list_lru_walk_node+0xc4/0x22c
|
|
binder_shrink_scan+0x108/0x1dc
|
|
shrinker_debugfs_scan_write+0x2b4/0x500
|
|
full_proxy_write+0xd4/0x140
|
|
vfs_write+0x1ac/0x758
|
|
ksys_write+0xf0/0x1dc
|
|
__arm64_sys_write+0x6c/0x9c
|
|
|
|
Allocated by task 492:
|
|
kmem_cache_alloc+0x130/0x368
|
|
vm_area_alloc+0x2c/0x190
|
|
mmap_region+0x258/0x18bc
|
|
do_mmap+0x694/0xa60
|
|
vm_mmap_pgoff+0x170/0x29c
|
|
ksys_mmap_pgoff+0x290/0x3a0
|
|
__arm64_sys_mmap+0xcc/0x144
|
|
|
|
Freed by task 491:
|
|
kmem_cache_free+0x17c/0x3c8
|
|
vm_area_free_rcu_cb+0x74/0x98
|
|
rcu_core+0xa38/0x26d4
|
|
rcu_core_si+0x10/0x1c
|
|
__do_softirq+0x2fc/0xd24
|
|
|
|
Last potentially related work creation:
|
|
__call_rcu_common.constprop.0+0x6c/0xba0
|
|
call_rcu+0x10/0x1c
|
|
vm_area_free+0x18/0x24
|
|
remove_vma+0xe4/0x118
|
|
do_vmi_align_munmap.isra.0+0x718/0xb5c
|
|
do_vmi_munmap+0xdc/0x1fc
|
|
__vm_munmap+0x10c/0x278
|
|
__arm64_sys_munmap+0x58/0x7c
|
|
|
|
Fix this issue by performing instead a vma_lookup() which will fail to
|
|
find the vma that was isolated before the mmap lock downgrade. Note that
|
|
this option has better performance than upgrading to a mmap write lock
|
|
which would increase contention. Plus, mmap_write_trylock() has been
|
|
recently removed anyway.(CVE-2023-52438)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
uio: Fix use-after-free in uio_open
|
|
|
|
core-1 core-2
|
|
-------------------------------------------------------
|
|
uio_unregister_device uio_open
|
|
idev = idr_find()
|
|
device_unregister(&idev->dev)
|
|
put_device(&idev->dev)
|
|
uio_device_release
|
|
get_device(&idev->dev)
|
|
kfree(idev)
|
|
uio_free_minor(minor)
|
|
uio_release
|
|
put_device(&idev->dev)
|
|
kfree(idev)
|
|
-------------------------------------------------------
|
|
|
|
In the core-1 uio_unregister_device(), the device_unregister will kfree
|
|
idev when the idev->dev kobject ref is 1. But after core-1
|
|
device_unregister, put_device and before doing kfree, the core-2 may
|
|
get_device. Then:
|
|
1. After core-1 kfree idev, the core-2 will do use-after-free for idev.
|
|
2. When core-2 do uio_release and put_device, the idev will be double
|
|
freed.
|
|
|
|
To address this issue, we can get idev atomic & inc idev reference with
|
|
minor_lock.(CVE-2023-52439)
|
|
|
|
NULL Pointer Dereference vulnerability in Linux Linux kernel kernel on Linux, x86, ARM (net, bluetooth modules) allows Overflow Buffers. This vulnerability is associated with program files /net/bluetooth/rfcomm/core.C.
|
|
|
|
This issue affects Linux kernel: v2.6.12-rc2.
|
|
|
|
(CVE-2024-22099)
|
|
|
|
In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion failure and crash because a subvolume can be read out too soon after its root item is inserted upon subvolume creation.(CVE-2024-23850)
|
|
|
|
copy_params in drivers/md/dm-ioctl.c in the Linux kernel through 6.7.1 can attempt to allocate more than INT_MAX bytes, and crash, because of a missing param_kernel->data_size check. This is related to ctl_ioctl.(CVE-2024-23851)
|
|
|
|
In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
tls: fix race between async notify and socket close
|
|
|
|
The submitting thread (one which called recvmsg/sendmsg)
|
|
may exit as soon as the async crypto handler calls complete()
|
|
so any code past that point risks touching already freed data.
|
|
|
|
Try to avoid the locking and extra flags altogether.
|
|
Have the main thread hold an extra reference, this way
|
|
we can depend solely on the atomic ref counter for
|
|
synchronization.
|
|
|
|
Don't futz with reiniting the completion, either, we are now
|
|
tightly controlling when completion fires.(CVE-2024-26583)</Note>
|
|
<Note Title="Topic" Type="General" Ordinal="4" xml:lang="en">An update for kernel is now available for openEuler-22.03-LTS.
|
|
|
|
openEuler Security has rated this update as having a security impact of high. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section.</Note>
|
|
<Note Title="Severity" Type="General" Ordinal="5" xml:lang="en">High</Note>
|
|
<Note Title="Affected Component" Type="General" Ordinal="6" xml:lang="en">kernel</Note>
|
|
</DocumentNotes>
|
|
<DocumentReferences>
|
|
<Reference Type="Self">
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1283</URL>
|
|
</Reference>
|
|
<Reference Type="openEuler CVE">
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52436</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52438</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2023-52439</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2024-22099</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2024-23850</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2024-23851</URL>
|
|
<URL>https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2024-26583</URL>
|
|
</Reference>
|
|
<Reference Type="Other">
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52436</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52438</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2023-52439</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2024-22099</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2024-23850</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2024-23851</URL>
|
|
<URL>https://nvd.nist.gov/vuln/detail/CVE-2024-26583</URL>
|
|
</Reference>
|
|
</DocumentReferences>
|
|
<ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
|
|
<Branch Type="Product Name" Name="openEuler">
|
|
<FullProductName ProductID="openEuler-22.03-LTS" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">openEuler-22.03-LTS</FullProductName>
|
|
</Branch>
|
|
<Branch Type="Package Arch" Name="aarch64">
|
|
<FullProductName ProductID="kernel-headers-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-headers-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-devel-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-devel-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="perf-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">perf-debuginfo-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-source-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-source-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-tools-debuginfo-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="python3-perf-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">python3-perf-debuginfo-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="perf-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">perf-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-devel-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-tools-devel-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-debugsource-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-debugsource-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="bpftool-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">bpftool-debuginfo-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-debuginfo-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="bpftool-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">bpftool-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-tools-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
<FullProductName ProductID="python3-perf-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">python3-perf-5.10.0-60.129.0.156.oe2203.aarch64.rpm</FullProductName>
|
|
</Branch>
|
|
<Branch Type="Package Arch" Name="src">
|
|
<FullProductName ProductID="kernel-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-5.10.0-60.129.0.156.oe2203.src.rpm</FullProductName>
|
|
</Branch>
|
|
<Branch Type="Package Arch" Name="x86_64">
|
|
<FullProductName ProductID="kernel-tools-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-tools-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="bpftool-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">bpftool-debuginfo-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-debugsource-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-debugsource-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="python3-perf-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">python3-perf-debuginfo-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-devel-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-tools-devel-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="perf-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">perf-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-headers-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-headers-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-debuginfo-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="python3-perf-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">python3-perf-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-devel-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-devel-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-tools-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-tools-debuginfo-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="kernel-source-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">kernel-source-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="perf-debuginfo-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">perf-debuginfo-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
<FullProductName ProductID="bpftool-5.10.0-60.129.0.156" CPE="cpe:/a:openEuler:openEuler:22.03-LTS">bpftool-5.10.0-60.129.0.156.oe2203.x86_64.rpm</FullProductName>
|
|
</Branch>
|
|
</ProductTree>
|
|
<Vulnerability Ordinal="1" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="1" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
f2fs: explicitly null-terminate the xattr list
|
|
|
|
When setting an xattr, explicitly null-terminate the xattr list. This
|
|
eliminates the fragile assumption that the unused xattr space is always
|
|
zeroed.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-03-15</ReleaseDate>
|
|
<CVE>CVE-2023-52436</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-22.03-LTS</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>4.5</BaseScore>
|
|
<Vector>AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-03-15</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1283</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="2" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="2" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
binder: fix use-after-free in shinker's callback
|
|
|
|
The mmap read lock is used during the shrinker's callback, which means
|
|
that using alloc->vma pointer isn't safe as it can race with munmap().
|
|
As of commit dd2283f2605e ("mm: mmap: zap pages with read mmap_sem in
|
|
munmap") the mmap lock is downgraded after the vma has been isolated.
|
|
|
|
I was able to reproduce this issue by manually adding some delays and
|
|
triggering page reclaiming through the shrinker's debug sysfs. The
|
|
following KASAN report confirms the UAF:
|
|
|
|
==================================================================
|
|
BUG: KASAN: slab-use-after-free in zap_page_range_single+0x470/0x4b8
|
|
Read of size 8 at addr ffff356ed50e50f0 by task bash/478
|
|
|
|
CPU: 1 PID: 478 Comm: bash Not tainted 6.6.0-rc5-00055-g1c8b86a3799f-dirty #70
|
|
Hardware name: linux,dummy-virt (DT)
|
|
Call trace:
|
|
zap_page_range_single+0x470/0x4b8
|
|
binder_alloc_free_page+0x608/0xadc
|
|
__list_lru_walk_one+0x130/0x3b0
|
|
list_lru_walk_node+0xc4/0x22c
|
|
binder_shrink_scan+0x108/0x1dc
|
|
shrinker_debugfs_scan_write+0x2b4/0x500
|
|
full_proxy_write+0xd4/0x140
|
|
vfs_write+0x1ac/0x758
|
|
ksys_write+0xf0/0x1dc
|
|
__arm64_sys_write+0x6c/0x9c
|
|
|
|
Allocated by task 492:
|
|
kmem_cache_alloc+0x130/0x368
|
|
vm_area_alloc+0x2c/0x190
|
|
mmap_region+0x258/0x18bc
|
|
do_mmap+0x694/0xa60
|
|
vm_mmap_pgoff+0x170/0x29c
|
|
ksys_mmap_pgoff+0x290/0x3a0
|
|
__arm64_sys_mmap+0xcc/0x144
|
|
|
|
Freed by task 491:
|
|
kmem_cache_free+0x17c/0x3c8
|
|
vm_area_free_rcu_cb+0x74/0x98
|
|
rcu_core+0xa38/0x26d4
|
|
rcu_core_si+0x10/0x1c
|
|
__do_softirq+0x2fc/0xd24
|
|
|
|
Last potentially related work creation:
|
|
__call_rcu_common.constprop.0+0x6c/0xba0
|
|
call_rcu+0x10/0x1c
|
|
vm_area_free+0x18/0x24
|
|
remove_vma+0xe4/0x118
|
|
do_vmi_align_munmap.isra.0+0x718/0xb5c
|
|
do_vmi_munmap+0xdc/0x1fc
|
|
__vm_munmap+0x10c/0x278
|
|
__arm64_sys_munmap+0x58/0x7c
|
|
|
|
Fix this issue by performing instead a vma_lookup() which will fail to
|
|
find the vma that was isolated before the mmap lock downgrade. Note that
|
|
this option has better performance than upgrading to a mmap write lock
|
|
which would increase contention. Plus, mmap_write_trylock() has been
|
|
recently removed anyway.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-03-15</ReleaseDate>
|
|
<CVE>CVE-2023-52438</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-22.03-LTS</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>High</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>7.0</BaseScore>
|
|
<Vector>AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-03-15</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1283</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="3" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="3" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
uio: Fix use-after-free in uio_open
|
|
|
|
core-1 core-2
|
|
-------------------------------------------------------
|
|
uio_unregister_device uio_open
|
|
idev = idr_find()
|
|
device_unregister(&idev->dev)
|
|
put_device(&idev->dev)
|
|
uio_device_release
|
|
get_device(&idev->dev)
|
|
kfree(idev)
|
|
uio_free_minor(minor)
|
|
uio_release
|
|
put_device(&idev->dev)
|
|
kfree(idev)
|
|
-------------------------------------------------------
|
|
|
|
In the core-1 uio_unregister_device(), the device_unregister will kfree
|
|
idev when the idev->dev kobject ref is 1. But after core-1
|
|
device_unregister, put_device and before doing kfree, the core-2 may
|
|
get_device. Then:
|
|
1. After core-1 kfree idev, the core-2 will do use-after-free for idev.
|
|
2. When core-2 do uio_release and put_device, the idev will be double
|
|
freed.
|
|
|
|
To address this issue, we can get idev atomic & inc idev reference with
|
|
minor_lock.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-03-15</ReleaseDate>
|
|
<CVE>CVE-2023-52439</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-22.03-LTS</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>High</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>7.0</BaseScore>
|
|
<Vector>AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-03-15</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1283</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="4" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="4" xml:lang="en">NULL Pointer Dereference vulnerability in Linux Linux kernel kernel on Linux, x86, ARM (net, bluetooth modules) allows Overflow Buffers. This vulnerability is associated with program files /net/bluetooth/rfcomm/core.C.This issue affects Linux kernel: v2.6.12-rc2.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-03-15</ReleaseDate>
|
|
<CVE>CVE-2024-22099</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-22.03-LTS</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-03-15</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1283</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="5" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="5" xml:lang="en">In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion failure and crash because a subvolume can be read out too soon after its root item is inserted upon subvolume creation.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-03-15</ReleaseDate>
|
|
<CVE>CVE-2024-23850</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-22.03-LTS</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-03-15</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1283</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="6" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="6" xml:lang="en">copy_params in drivers/md/dm-ioctl.c in the Linux kernel through 6.7.1 can attempt to allocate more than INT_MAX bytes, and crash, because of a missing param_kernel->data_size check. This is related to ctl_ioctl.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-03-15</ReleaseDate>
|
|
<CVE>CVE-2024-23851</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-22.03-LTS</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.5</BaseScore>
|
|
<Vector>AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-03-15</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1283</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
<Vulnerability Ordinal="7" xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1">
|
|
<Notes>
|
|
<Note Title="Vulnerability Description" Type="General" Ordinal="7" xml:lang="en">In the Linux kernel, the following vulnerability has been resolved:
|
|
|
|
tls: fix race between async notify and socket close
|
|
|
|
The submitting thread (one which called recvmsg/sendmsg)
|
|
may exit as soon as the async crypto handler calls complete()
|
|
so any code past that point risks touching already freed data.
|
|
|
|
Try to avoid the locking and extra flags altogether.
|
|
Have the main thread hold an extra reference, this way
|
|
we can depend solely on the atomic ref counter for
|
|
synchronization.
|
|
|
|
Don't futz with reiniting the completion, either, we are now
|
|
tightly controlling when completion fires.</Note>
|
|
</Notes>
|
|
<ReleaseDate>2024-03-15</ReleaseDate>
|
|
<CVE>CVE-2024-26583</CVE>
|
|
<ProductStatuses>
|
|
<Status Type="Fixed">
|
|
<ProductID>openEuler-22.03-LTS</ProductID>
|
|
</Status>
|
|
</ProductStatuses>
|
|
<Threats>
|
|
<Threat Type="Impact">
|
|
<Description>Medium</Description>
|
|
</Threat>
|
|
</Threats>
|
|
<CVSSScoreSets>
|
|
<ScoreSet>
|
|
<BaseScore>5.1</BaseScore>
|
|
<Vector>AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H</Vector>
|
|
</ScoreSet>
|
|
</CVSSScoreSets>
|
|
<Remediations>
|
|
<Remediation Type="Vendor Fix">
|
|
<Description>kernel security update</Description>
|
|
<DATE>2024-03-15</DATE>
|
|
<URL>https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1283</URL>
|
|
</Remediation>
|
|
</Remediations>
|
|
</Vulnerability>
|
|
</cvrfdoc> |