ghsa-cp4f-3979-2g6x
Vulnerability from github
Published
2024-07-30 09:31
Modified
2024-07-30 09:31
Details

In the Linux kernel, the following vulnerability has been resolved:

igc: fix a log entry using uninitialized netdev

During successful probe, igc logs this:

[ 5.133667] igc 0000:01:00.0 (unnamed net_device) (uninitialized): PHC added ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The reason is that igc_ptp_init() is called very early, even before register_netdev() has been called. So the netdev_info() call works on a partially uninitialized netdev.

Fix this by calling igc_ptp_init() after register_netdev(), right after the media autosense check, just as in igb. Add a comment, just as in igb.

Now the log message is fine:

[ 5.200987] igc 0000:01:00.0 eth0: PHC added

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2024-42116",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-07-30T08:15:03Z",
      severity: null,
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\nigc: fix a log entry using uninitialized netdev\n\nDuring successful probe, igc logs this:\n\n[    5.133667] igc 0000:01:00.0 (unnamed net_device) (uninitialized): PHC added\n                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\nThe reason is that igc_ptp_init() is called very early, even before\nregister_netdev() has been called. So the netdev_info() call works\non a partially uninitialized netdev.\n\nFix this by calling igc_ptp_init() after register_netdev(), right\nafter the media autosense check, just as in igb.  Add a comment,\njust as in igb.\n\nNow the log message is fine:\n\n[    5.200987] igc 0000:01:00.0 eth0: PHC added",
   id: "GHSA-cp4f-3979-2g6x",
   modified: "2024-07-30T09:31:52Z",
   published: "2024-07-30T09:31:52Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-42116",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/86167183a17e03ec77198897975e9fdfbd53cb0b",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/96839f3f588236593de36465f142b0126267f8b6",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/98c8958980e829f023a490b9a9816ca1fe2f8b79",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/991f036cabc3d13e886a37faeea1b6800181fdda",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/d478ec838cf2b1e1051a8709cfc744fe1c03110f",
      },
   ],
   schema_version: "1.4.0",
   severity: [],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.