From: Ulrich Hecht <uli@fpond.eu>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@denx.de" <pavel@denx.de>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"masami.ichikawa@cybertrust.co.jp"
<masami.ichikawa@cybertrust.co.jp>,
"chris.paterson2@renesas.com" <chris.paterson2@renesas.com>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: [ANNOUNCE] Release v4.4.302-cip104
Date: Thu, 30 Oct 2025 11:03:00 +0100 (CET) [thread overview]
Message-ID: <2115994085.174609.1761818580269@webmail.strato.de> (raw)
Hi,
the CIP kernel team has released Linux kernel v4.4.302-cip104. The linux-4.4.y-cip tree's base version has been updated to v4.4-st69. The trees are up-to-date with kernel 4.19-st9.
You can get this release via the git tree or as a tarball from https://mirrors.edge.kernel.org/pub/linux/kernel/projects/cip/4.4/
v4.4.302-cip104:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.4.y-cip
commit hash:
9e1869f0ddca0c8329895558db8a18b0f7558b3c
Fixed CVEs:
CVE-2025-23143: net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod.
CVE-2025-37968: iio: light: opt3001: fix deadlock due to concurrent flag access
CVE-2025-39839: batman-adv: fix OOB read/write in network-coding decode
CVE-2025-39846: pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region()
CVE-2025-39847: ppp: fix memory leak in pad_compress_skb
CVE-2025-39848: ax25: properly unshare skbs in ax25_kiss_rcv()
CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen()
CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map
CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call
CVE-2025-39902: mm/slub: avoid accessing metadata when pointer is invalid in object_err()
CVE-2025-39911: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path
CVE-2025-39920: pcmcia: Add error handling for add_interval() in do_validate_mem()
CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task
CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font
CVE-2025-39986: can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow
CVE-2025-40011: drm/gma500: Fix null dereference in hdmi teardown
CVE-2025-40020: can: peak_usb: fix shift-out-of-bounds issue
Best regards,
Ulrich Hecht
reply other threads:[~2025-10-30 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2115994085.174609.1761818580269@webmail.strato.de \
--to=uli@fpond.eu \
--cc=chris.paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=masami.ichikawa@cybertrust.co.jp \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox