All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Ichikawa <masami.ichikawa@miraclelinux.com>
To: cip-dev <cip-dev@lists.cip-project.org>
Subject: [kernel-cve-report] New CVE entries this week
Date: Thu, 14 Mar 2024 08:34:09 +0900	[thread overview]
Message-ID: <CAODzB9pR7_5jsyfTTUnENOv5Y4GPcNSDnApcjyo3Xx8_-AjhiQ@mail.gmail.com> (raw)

Hi!

It's this week's CVE report.

This week reported 5 new CVEs and 8 updated CVEs.

* New CVEs

CVE-2023-28746: Register File Data Sampling (RFDS)

Announce: https://www.openwall.com/lists/oss-security/2024/03/12/13
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE was published by the Xen.org security team.

You can check which Intel processors are affected via Intel "Affected
Processors: Guidance for Security Issues on Intel® Processors".
(https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/processors-affected-consolidated-product-cpu-model.html)

Fixed by commit e95df4ec0c0c9791941f112db699fae794b9862a,
4e42765d1be01111df0c0275bbaf1db1acef346e,
8076fcde016c9c0e0660543e67bff86cb48a7c9c, and
2a0180129d726a4b953232175857d442651b55a0 in master branch.


Fixed status
mainline: [e95df4ec0c0c9791941f112db699fae794b9862a,
4e42765d1be01111df0c0275bbaf1db1acef346e,
8076fcde016c9c0e0660543e67bff86cb48a7c9c,
2a0180129d726a4b953232175857d442651b55a0]

CVE-2024-2193: GhostRace: Speculative Race Conditions

Announce: https://www.openwall.com/lists/oss-security/2024/03/12/14
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

This CVE was published by the Xen.org security team.

According to the researcher's report
(https://www.vusec.net/projects/ghostrace/) it said that
"""
The Linux kernel developers have no immediate plans to implement our
proposed serialization of synchronization primitives due to
performance concerns. However, they confirmed the IPI storming issue
(CVE-2024-26602) and implemented an IPI rate-limiting feature
to address the CPU saturation issue by adding a synchronization mutex
on the path of sys_membarrier and avoiding its concurrent
execution on multiple cores. Unfortunately, as our experiments show
(Figure 4), hindering IPI storming primitives (i.e., 0 storming cores)
is insufficient to close the attack surface completely.
"""

Fixed status
Not fixed yet

CVE-2023-52608: firmware: arm_scmi: Check mailbox/SMT channel for consistency

Announce: https://lore.kernel.org/linux-cve-announce/20240313140155.1913910-3-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit 5c8a47a ("firmware: arm_scmi: Make scmi core
independent of the transport type") in v5.7-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc2.

Fixed status
mainline: [437a310b22244d4e0b78665c3042e5d1c0f45306]
stable/5.15: [614cc65032dcb0b64d23f5c5e338a8a04b12be5d]
stable/6.1: [7f95f6997f4fdd17abec3200cae45420a5489350]
stable/6.6: [9b5e1b93c83ee5fc9f5d7bd2d45b421bd87774a2]
stable/6.7: [12dc4217f16551d6dee9cbefc23fdb5659558cda]

CVE-2024-26629: nfsd: fix RELEASE_LOCKOWNER

Announce: https://lore.kernel.org/linux-cve-announce/20240313140155.1913910-4-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit ce3c4ad ("NFSD: Fix possible sleep during
nfsd4_release_lockowner()") in v5.19-rc1.
This commit is backported to 4.4, 4.19, 5.4, 5.10, and 5.15. All
stable kernels are affected.
Fixed in v6.8-rc2.

Fixed status
mainline: [edcf9725150e42beeca42d085149f4c88fa97afd]
stable/6.1: [e4cf8941664cae2f89f0189c29fe2ce8c6be0d03]
stable/6.6: [b7d2eee1f53899b53f069bba3a59a419fc3d331b]
stable/6.7: [8f5b860de87039b007e84a28a5eefc888154e098]

CVE-2024-26630: mm: cachestat: fix folio read-after-free in cache walk

Announce: https://lore.kernel.org/linux-cve-announce/20240313155037.1968072-2-lee@kernel.org/
CVSS v3(NIST): N/A
CVSS v3(CNA): N/A

Introduced by commit cf264e1 ("cachestat: implement cachestat
syscall") in v6.5-rc1.
This commit is not backported to older stable kernels.
Fixed in v6.8-rc7.

Fixed status
mainline: [3a75cb05d53f4a6823a32deb078de1366954a804]
stable/6.6: [ba60fdf75e89ea762bb617be578dc47f27655117]
stable/6.7: [fe7e008e0ce728252e4ec652cceebcc62211657c]


* Updated CVEs

CVE-2023-6356: NULL pointer dereference in nvmet_tcp_build_iovec

The mainline and all stable kernels are fixed. Linux 4.x is not affected.

Fixed status
mainline: [efa56305908ba20de2104f1b8508c6a7401833be]
stable/5.10: [f775f2621c2ac5cc3a0b3a64665dad4fb146e510]
stable/5.15: [4cb3cf7177ae3666be7fb27d4ad4d72a295fb02d]
stable/5.4: [ee5e7632e981673f42a50ade25e71e612e543d9d]
stable/6.1: [2871aa407007f6f531fae181ad252486e022df42]
stable/6.6: [24e05760186dc070d3db190ca61efdbce23afc88]
stable/6.7: [70154e8d015c9b4fb56c1a2ef1fc8b83d45c7f68]

CVE-2023-6536: NULL pointer dereference in __nvmet_req_complete

The mainline and all stable kernels are fixed. Linux 4.x is not affected.

Fixed status
mainline: [0849a5441358cef02586fb2d60f707c0db195628]
stable/5.10: [39669fae69f302961d89f38d969c6fcc1d07eb02]
stable/5.15: [0613a2fbdf8d32c3f8f1e62d704e92251a100795]
stable/5.4: [9638beb4e10ac116c6a4fc13315e9c3608055ac0]
stable/6.1: [83ccd15717ee2b6143df72df39685f0c832e3451]
stable/6.6: [2f00fd8d50a7d5eedc85e62efdc1a29213168998]
stable/6.7: [c32d355f507fa81cf23aaa4dd4150e696cb8ebaf]

CVE-2024-0841: hugetlbfs: Null pointer dereference in
hugetlbfs_fill_super function

The mainline and all stable kernels are fixed. Linux 4.x is not affected.

Fixed status
mainline: [79d72c68c58784a3e1cd2378669d51bfd0cb7498]
stable/5.10: [80d852299987a8037be145a94f41874228f1a773]
stable/5.15: [22850c9950a4e43a67299755d11498f3292d02ff]
stable/5.4: [1dde8ef4b7a749ae1bc73617c91775631d167557]
stable/6.1: [2e2c07104b4904aed1389a59b25799b95a85b5b9]
stable/6.6: [13c5a9fb07105557a1fa9efdb4f23d7ef30b7274]
stable/6.7: [ec78418801ef7b0c22cd6a30145ec480dd48db39]

Currently tracking CVEs

CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
Bluetooth Core Specifications 4.0 through 5.2

There is no fix information.

CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
Provisioning Leads to MITM

No fix information.

CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning

No fix information.

CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning

No fix information.

Regards,
-- 
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com


             reply	other threads:[~2024-03-13 23:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 23:34 Masami Ichikawa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-23  0:56 [kernel-cve-report] New CVE entries this week Masami Ichikawa
2024-05-23  6:12 ` Jan Kiszka
2024-05-15 22:11 Masami Ichikawa
2024-05-08 23:45 Masami Ichikawa
2024-05-02  3:10 Masami Ichikawa
2024-04-24 22:53 Masami Ichikawa
2024-04-18  4:09 Masami Ichikawa
2024-04-11  2:21 Masami Ichikawa
2024-04-04  5:34 Masami Ichikawa
2024-03-27 23:10 Masami Ichikawa
2024-03-20 23:36 Masami Ichikawa
2024-03-07  3:08 Masami Ichikawa
2024-02-29  0:02 Masami Ichikawa
2024-02-22  0:31 Masami Ichikawa
2024-02-14 22:47 Masami Ichikawa
2024-02-07 23:05 Masami Ichikawa
2024-01-31 23:18 Masami Ichikawa
2024-01-24 23:17 Masami Ichikawa
2024-01-10 22:52 Masami Ichikawa
2024-01-03 23:09 Masami Ichikawa
2023-12-27 22:47 Masami Ichikawa
2023-12-20 23:08 Masami Ichikawa
2023-12-13 22:52 Masami Ichikawa
2023-12-06 23:22 Masami Ichikawa
2023-11-29 23:03 Masami Ichikawa
2023-11-22 23:21 Masami Ichikawa
2023-11-15 22:48 Masami Ichikawa
2023-11-08 22:55 Masami Ichikawa
2023-11-01 22:42 Masami Ichikawa
2023-10-25 23:30 Masami Ichikawa
2023-10-18 23:20 Masami Ichikawa
2023-10-11 22:54 Masami Ichikawa
2023-10-04 22:09 Masami Ichikawa
2023-09-27 22:58 Masami Ichikawa
2023-09-20 22:51 Masami Ichikawa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAODzB9pR7_5jsyfTTUnENOv5Y4GPcNSDnApcjyo3Xx8_-AjhiQ@mail.gmail.com \
    --to=masami.ichikawa@miraclelinux.com \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.