Changes between Version 35 and Version 36 of linux/kernel

Timestamp:

05/13/2026 11:42:31 PM (7 weeks ago)

Author:

Ryan Erb

Comment:

add note for CVE

linux/kernel

@@ -506 +506 @@
 = Make HELP
 
-Executing "make help" in your kernel build directory will provide a complete list of available targets with explanations.  This list will also include available defconfigs.    
+Executing "make help" in your kernel build directory will provide a complete list of available targets with explanations.  This list will also include available defconfigs.
+
+= Linux Kernel Security Updates / CVE
+
+Security fixes are constantly being made for Linux. These are referred to as Common Vulnerabilities and Exposures (CVE). There are many CVEs that do not apply to Gateworks use cases. There are some that do. 
+
+Given the mass amount of CVE's, Gateworks does not constantly update to include each and every one. Patches for CVE's are usually included in minor kernel release versions. 
+
+It is up to Gateworks customers to apply whichever patches they need when they need them. 
+
+The best way to do this is to update to the latest Linux Kernel release (assuming it has the CVE fix) and then applying the Gateworks patches on top. 
+
+Gateworks provides patches on top of Linux LTS kernels for its product families and partiicipates in kernel development by submitting these via the kernel patch submission process. While Gateworks does not rebase its patches on top of each and every new stable kernel release (as these can release on a weekly basis) it is generally very easy to rebase the Gateworks patches on top of the latest LTS stable kernels. For example for the Venice SBCs:
+{{{
+git clone https://github.com/Gateworks/linux-venice.git
+cd linux-venice
+git checkout v6.18-5.venice
+git remote add stable git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
+git remote update
+git checkout -b v6.18.y-venice
+git rebase -i remotes/stable/linux-6.18.y    
+}}}