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, 9 Nov 2023 07:55:54 +0900	[thread overview]
Message-ID: <CAODzB9q1AOFqyaKhEpdFmFzpXj6vu8Ve4FhT3Q7Ra4VPJ=9JWw@mail.gmail.com> (raw)

Hi!

It's this week's CVE report.

This week reported 1 new CVEs and 7 updated CVEs.

* New CVEs

CVE-2023-47233: Use after Free bug in brcmf_cfg80211_detach

CVSS v3(NIST): N/A

The brcm80211 component in the Linux kernel through 6.5.10 has a
brcmf_cfg80211_detach use-after-free in the device unplugging
(disconnect the USB by hotplug) code. For physically proximate
attackers with local access, this "could be exploited in a real world
scenario." This is related to brcmf_cfg80211_escan_timeout_worker in
drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c.

Introduced by commit e756af5 ("brcmfmac: add e-scan support.") in 3.7-rc1.

Fixed status
Not fixed yet

* Updated CVEs

CVE-2023-46862: io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid

Stable 6.1 and 6.5 were fixed.

Fixed status
mainline: [7644b1a1c9a7ae8ab99175989bfc8676055edb46]
stable/6.1: [9236d2ea6465b37c0a73d994c1ad31753d31e5f5]
stable/6.5: [56e08ccc969796168f0e6adf6642f8546f54ba6f]

CVE-2023-5158: vringh: don''t use vringh_kiov_advance() in vringh_iov_xfer()

Fixed in mainline, 5.15, 6.1, and 6.5.

Fixed status
mainline: [7aed44babc7f97e82b38e9a68515e699692cc100]
stable/5.15: [1e69422efcc60571cc04f6c1940da848a8c2f21b]
stable/6.1: [3a72decd6b49ff11a894aabd4d9b3025f046fe61]
stable/6.5: [0bf2b9c2f3545ffce5720de61c33fc171c0e480a]

CVE-2021-44879: f2fs: fix to do sanity check on inode type during
garbage collection

Stable 4.14, 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [9056d6489f5a41cfbb67f719d2c0ce61ead72d9f]
stable/4.14: [a481db81e7ead1369acca8e13b6939778cb7d2c5]
stable/4.19: [45c9da086dded78a12bc580f5bb012545a910803]
stable/5.10: [571ce7d944cdd204da163cb5d5cc75bb38090246]
stable/5.15: [0ddbdc0b7f0cec3815ac05a30b2c2f6457be3050]
stable/5.16: [d667b9f61df7bdfcb59dd1406fd2392c358f0008]
stable/5.4: [e9a988cd4c8baac7550aa0c2f1efc9533ed9da36]

CVE-2023-3567: use-after-free in vcs_read in drivers/tty/vt/vc_screen.c

Stable 4.14 was fixed.

Fixed status
mainline: [226fae124b2dac217ea5436060d623ff3385bc34]
stable/4.14: [af79ea9a2443016f64d8fd8d72020cc874f0e066]
stable/4.19: [6332f52f44b9776568bf3c0b714ddfb0bb175e78]
stable/5.10: [55515d7d8743b71b80bfe68e89eb9d92630626ab]
stable/5.15: [fc9e27f3ba083534b8bbf72ab0f5c810ffdc7d18]
stable/5.4: [d0332cbf53dad06a22189cc341391237f4ea6d9f]
stable/6.1: [8506f16aae9daf354e3732bcfd447e2a97f023df]

CVE-2023-45863: kobject: Fix slab-out-of-bounds in fill_kobj_path()

Stable 4.14, 4.19, 5.10, and 5.4 were fixed.

Fixed status
mainline: [3bb2a01caa813d3a1845d378bbe4169ef280d394]
stable/4.14: [b43cf5ad5241d6f33a02c93271a282d5ed6c4cce]
stable/4.19: [0af6c6c15681cf80aeb85fcb3a1928c63aa89deb]
stable/5.10: [b2e62728b106fe54f8618c21a252df7d4a4cc775]
stable/5.15: [89a0079049f5568268d75c8cdf28bec0e2553e23]
stable/5.4: [5776aeee2a604ccc03e8269713624f9c8fd318e0]
stable/6.1: [fe4dd80d58ec5633daf5d50671d1341f738508bf]

CVE-2023-5090: x86: KVM: SVM: always update the x2avic msr interception

Stable 6.1 was fixed.

Fixed status
mainline: [b65235f6e102354ccafda601eaa1c5bef5284d21]
stable/6.1: [7ab62e3415fb59289ab6dea31f0cc0237b949200]
stable/6.5: [94805f9d3a3fb1f091bcc08b9c4846c4346706eb]

CVE-2023-5178: nvmet-tcp: Fix a possible UAF in queue intialization setup

Stable 5.4 was fixed.

Fixed status
mainline: [d920abd1e7c4884f9ecd0749d1921b7ab19ddfbd]
stable/5.10: [e985d78bdcf37f7ef73666a43b0d2407715f00d3]
stable/5.15: [34f62612be2a7f90ab68a14154db6664a32f8db0]
stable/5.4: [4e53bab11f01a401a5acd3bc94335b27ec79106b]
stable/6.1: [f691ec5a548257edb3aacd952e2a574e4e57b2c4]
stable/6.5: [675f0e9bb716fa3252979145b9b1a950140e94e9]

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:[~2023-11-08 22:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 22:55 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-13 23:34 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-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='CAODzB9q1AOFqyaKhEpdFmFzpXj6vu8Ve4FhT3Q7Ra4VPJ=9JWw@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.