You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
Thank you so much for the information !! If my version is up to date, why my security scans are showing many vulnerabilities. I am using apt update && apt upgrade to install updates. Do i need to do anything different ? NOTE :These are production servers.S Zaff– S Zaff2025-05-17 02:47:46 +00:00Commented May 17, 2025 at 2:47
-
2Because most vulnerability scanners only look at the version number 6.8.0 and are not capable of distinguishing the patches applied on top. 6.8 is not an Linux kernel LTS, and the major distributions maintain their own patches. Most fixes are a couple on lines of code, but once compiled it is hard to trace back if a certain patch was applied. Hence the many falso positives from your scanner.sleepyhead– sleepyhead2025-05-17 04:15:07 +00:00Commented May 17, 2025 at 4:15
-
2@SZaff sleepyhead is correct, partially. Your security scanners are likely NOT tuned to check package versions (especially if doing scans external to the system) and are likely NOT seeing things. THIS SAID, you are not up to date. You're up to date against CVE-2024-38541, but not other security patches and bug fixes in the kernel trees. During your next maintenance window, you should update these servers with the updated kernel and then reboot them. Production or not, security needs to be handled usually during scheduled maintenance windows.Thomas Ward– Thomas Ward ♦2025-05-17 18:02:00 +00:00Commented May 17, 2025 at 18:02
-
Thank you for the support guys. much appreciated, i will reach out to our security team with all these details.S Zaff– S Zaff2025-05-20 15:05:14 +00:00Commented May 20, 2025 at 15:05
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. command-line), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you