From: Pavel Machek <pavel@nabladev.com>
To: whyshall.dev@gmail.com
Cc: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] Urgent: Regarding Fixing of Security Vulnerabilities
Date: Mon, 13 Jul 2026 23:08:59 +0200 [thread overview]
Message-ID: <alVT63ojQwHf4n7f@duo.ucw.cz> (raw)
In-Reply-To: <Groupsio.1.CAOksrezPuEAoJ86FHMS_ajoH0h7pe3usksyo84n5rF9RKHfu4g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Hi!
> We are planning to migrate our product to the Linux Kernel 4.19.y
>CIP release to benefit from its long-term maintenance and security
>updates.
Would you mind introducing yourself, your company, and your product?
Normally, we would recommend 6.12 kernel branch if you are doing the
migration, anyway.
> We have a few questions regarding security vulnerability tracking for the CIP kernel:
>
> * Is there any tool, dashboard, or documentation available to determine:
>
> * The Kernel CVEs applicable to a specific 4.19.y CIP release.
> * Which CVEs have already been fixed till the given CIP release.
> * Which CVEs are still outstanding.
Take a look at
git@gitlab.com:cip-project/cip-kernel/cip-kernel-sec.git .
> * If there are unfixed vulnerabilities that are considered critical
> for our product, what is the recommended approach to address them?
Approach is similar / same to what -stable kernels use.
Best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-07-13 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 4:53 Urgent: Regarding Fixing of Security Vulnerabilities whyshall
2026-07-09 9:13 ` whyshall.dev
[not found] ` <Groupsio.1.CAOksrezPuEAoJ86FHMS_ajoH0h7pe3usksyo84n5rF9RKHfu4g@mail.gmail.com>
2026-07-13 21:08 ` Pavel Machek [this message]
2026-07-14 5:10 ` whyshall
2026-07-14 7:48 ` whyshall
2026-07-16 10:48 ` whyshall
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=alVT63ojQwHf4n7f@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=whyshall.dev@gmail.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