From: Ulrich Hecht <uli@fpond.eu>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@nabladev.com" <pavel@nabladev.com>,
"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>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: [ANNOUNCE] Release v4.4.302-cip106
Date: Thu, 8 Jan 2026 04:01:01 +0100 (CET) [thread overview]
Message-ID: <412566056.426263.1767841261029@webmail.strato.de> (raw)
Hi,
the CIP kernel team has released Linux kernel v4.4.302-cip106. The linux-4.4.y-cip tree's base version has been updated to v4.4-st71. The trees are up-to-date with kernel 4.19-st11.
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-cip106:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.4.y-cip
commit hash:
c97310ca688eb68384906f39428c5ed41f27ef86
Fixed CVEs:
CVE-2024-47666: scsi: pm80xx: Set phy->enable_completion only when we wait for it
CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty()
CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise
CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue
CVE-2025-40211: ACPI: video: Fix use-after-free in acpi_video_switch_brightness()
CVE-2025-40253: s390/ctcm: Fix double-kfree
CVE-2025-40259: scsi: sg: Do not sleep in atomic context
CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC
CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de()
CVE-2025-40281: sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto
CVE-2025-40282: Bluetooth: 6lowpan: reset link-local header on ipv6 recv path
CVE-2025-40283: Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF
CVE-2025-40304: fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds
CVE-2025-40308: Bluetooth: bcsp: receive data only if registered
CVE-2025-40309: Bluetooth: SCO: Fix UAF on sco_conn_free
CVE-2025-40312: jfs: Verify inode mode when loading from disk
CVE-2025-40321: wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode
CVE-2025-40322: fbdev: bitblit: bound-check glyph index in bit_putcs*
CVE-2025-40345: usb: storage: sddr55: Reject out-of-bound new_pba
CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output
CVE-2025-68168: jfs: fix uninitialized waitqueue in transaction manager
CVE-2025-68177: cpufreq/longhaul: handle NULL policy in longhaul_exit
CVE-2025-68185: nfs4_setup_readdir(): insufficient locking for ->d_parent->d_inode dereferencing
CVE-2025-68194: media: imon: make send_packet() more robust
CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe
CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup
CVE-2025-68288: usb: storage: Fix memory leak in USB bulk transport
CVE-2025-68289: usb: gadget: f_eem: Fix memory leak in eem_unwrap
CVE-2025-68302: net: sxgbe: fix potential NULL dereference in sxgbe_rx()
CVE-2025-68312: usbnet: Prevents free active kevent
CVE-2025-68331: usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer
CVE-2025-68339: atm/fore200e: Fix possible data race in fore200e_open()
CVE-2025-68734: isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()
Best regards,
Ulrich Hecht
reply other threads:[~2026-01-08 3:01 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=412566056.426263.1767841261029@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=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.com \
/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