{"metadata": {"vulnerability": "CVE-2026-99281", "count": 10, "kinds": {"milestone": 4, "sighting": 1, "kev": 0, "other": 5}}, "data": [{"timestamp": "2026-09-25T10:25:14.405Z", "date_only": false, "value": "2026-09-25T10:25:14.405Z", "kind": "milestone", "label": "Reserved", "source": "cvelistv5", "record": "CVE-2026-99281", "field": "cveMetadata.dateReserved"}, {"timestamp": "2026-11-07T14:08:47.735Z", "date_only": false, "value": "2026-11-07T14:08:47.735Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99281", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, {"timestamp": "2026-11-07T14:08:47.735Z", "date_only": false, "value": "2026-11-07T14:08:47.735Z", "kind": "other", "label": "Updated", "source": "cvelistv5", "record": "CVE-2026-99281", "field": "cveMetadata.dateUpdated"}, {"timestamp": "2026-11-07T14:08:47.735Z", "date_only": false, "value": "2026-11-07T14:08:47.735Z", "kind": "other", "label": "Updated", "source": "cvelistv5 / Linux", "record": "CVE-2026-99281", "field": "containers.cna.providerMetadata.dateUpdated"}, {"timestamp": "2026-11-07T14:17:03Z", "date_only": false, "value": "2026-11-07T14:17:03Z", "kind": "other", "label": "Nvd published at", "source": "github \u00b7 GHSA-CFRF-W8R8-RF8X", "record": "GHSA-CFRF-W8R8-RF8X", "field": "database_specific.nvd_published_at", "linked_record": true}, {"timestamp": "2026-11-07T14:17:03.790Z", "date_only": false, "value": "2026-11-07T14:17:03.790", "kind": "milestone", "label": "Published", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99281", "record": "FKIE_CVE-2026-99281", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-07T14:17:03.790Z", "date_only": false, "value": "2026-11-07T14:17:03.790", "kind": "other", "label": "Updated", "source": "fkie_nvd \u00b7 FKIE_CVE-2026-99281", "record": "FKIE_CVE-2026-99281", "field": "lastModified", "linked_record": true}, {"timestamp": "2026-11-07T14:21:47.406Z", "date_only": false, "value": "2026-11-07T14:21:47.406049Z", "kind": "sighting", "label": "Seen", "source": "https://infosec.exchange/users/cve/statuses/117575601801899411", "record": "CVE-2026-99281", "field": "creation_timestamp", "uuid": "af90e8eb-f8b9-45ad-a1a9-6f7c6a87b3f1", "content": "CVE-2026-99281 tun: Require CAP_NET_ADMIN to attach to an ownerless device In the Linux kernel, the following vulnerability has been resolved:\ntun: Require CAP_NET_ADMIN to attach to an ownerless device\nTwenty years ago I made creating a tuntap device require CAP_NET_ADMINin commit ca6bb5d7ab22 (\"[NET]: Require CAP_NET_ADMIN to create tuntapdevices.\")\nThe idea was to allow the permissions on /dev/net/tun to be relaxed to0666 and thus allow owners of tun devices assigned with TUNSETOWNER toactually open it and get at their devices.\nWhat we missed at the time was that persistent devices with *no* ownerwere already essentially world-consumable, and anyone who could openthe device node could also attach to those.\nEven then, using persistent devices with no explicitly set owner \u2014 onthe (false) presumption that CAP_NET_ADMIN would be required to openthem \u2014 wasn't an egregious userspace bug. There are cases where it doesmake sense to separate the creation/configuration of the netdevice, fromthe process which shovels packets into it.\nSince then, TUNSETGROUP was added a year later in commit 8c644623fe7e(\"[NET]: Allow group ownership of TUN/TAP devices.\"). Its commit messagenoted that if both uid and gid are set, both have to match (in itself abizarre choice) \u2014 but still not that with *neither* set, no permissionat all was required.\nThen in 2012 commit c8d68e6be1c3 (\"tuntap: multiqueue support\") allowednew queues to be attached to a device from the moment of its creation,with no way for userspace to close the race between creation and asubsequent TUNSET{OWNER,GROUP}.\nIn 2024, commit 3ca459eaba1bf (\"tun: fix group permission check\") triedto fix things to be saner: only require the user *or* the group tomatch, in line with standard POSIX permissions, and requireCAP_NET_ADMIN if neither the user nor group authorised the access(although it put the CAP_NET_ADMIN check first, and would wrongly havereported the capability as having been used even when it was not).\nThat fix was reverted in commit a70c7b3cbc06 (\"tun: revert fix grouppermission check\") due to allegedly causing a regression in an selinuxtest suite which *expected* the attachment to succeed when authorisedby none of user, group, nor CAP_NET_ADMIN:https://lore.kernel.org/netdev/CAFqZXNtkCBT4f+PwyVRmQGoT3p1eVa01fCG_aNtpt6dakXncUg@mail.gmail.com/\nWe should not break UAPI. But we don't have to consider an selinux testcase which deliberately exercises a security flaw to be UAPI worthpreserving either. To which end, I have fixed it in selinux-testsuitecommit b2f894f0016b (\"tests/tun_tap: set an owner on the device for therelabel tests\").\nSo: fix the lack of CAP_NET_ADMIN check on devices which *haven't* beenassigned an owner or group, while leaving the weird tun ownership modelas it was (user *and* group have to match, if both are set). If someonestill wants to fix the latter (which wasn't actually the reason theprevious attempt was reverted), they can do it under separate cover.\nPermit attaching to an existing device only if an owner and/or group wasset and the caller matches all that were set, or if the caller hasCAP_NET_ADMIN. The only behavioural change is that a device with noowner or group now requires CAP_NET_ADMIN to attach \u2014 precisely theloophole we want to close.\nAnd put the CAP_NET_ADMIN check in the right place this time.\nhttps://www.cve.org/CVERecord?id=CVE-2026-99281https://git.kernel.org/stable/c/2f92c0286cfd58bff9d6d54c01a771073d5eb775https://git.kernel.org/stable/c/e53d1cf05da8ea58a5743b7ce5894fb51b0b9700https://git.kernel.org/stable/c/ffdf678dd16610e3f006dac904bd37c09684673c#kernel #Linux#CVE_2026_99281#bot", "url": "https://infosec.exchange/users/cve/statuses/117575601801899411"}, {"timestamp": "2026-11-07T15:30:28Z", "date_only": false, "value": "2026-11-07T15:30:28Z", "kind": "milestone", "label": "Published", "source": "github \u00b7 GHSA-CFRF-W8R8-RF8X", "record": "GHSA-CFRF-W8R8-RF8X", "field": "published", "metric_role": "disclosure", "metric_basis": "recorded_event", "linked_record": true}, {"timestamp": "2026-11-07T15:30:29Z", "date_only": false, "value": "2026-11-07T15:30:29Z", "kind": "other", "label": "Updated", "source": "github \u00b7 GHSA-CFRF-W8R8-RF8X", "record": "GHSA-CFRF-W8R8-RF8X", "field": "modified", "linked_record": true}], "metrics": {"as_of": "2026-11-07T21:04:24.912Z", "anchors": {"origin": {"timestamp": "2026-11-07T14:08:47.735Z", "date_only": false, "value": "2026-11-07T14:08:47.735Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99281", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "discovery": null, "report": null, "acknowledgement": null, "disclosure": {"timestamp": "2026-11-07T14:08:47.735Z", "date_only": false, "value": "2026-11-07T14:08:47.735Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99281", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "exploit_publication": null, "exploitation": null, "patch": null}, "vendor_response_time": {"available": false, "missing": ["start", "end"]}, "time_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit": {"available": false, "missing": ["end"]}, "disclosure_to_exploit_publication": {"available": false, "missing": ["end"]}, "time_to_patch": {"available": false, "missing": ["start", "end"]}, "total_time_to_patch": {"available": false, "missing": ["start", "end"]}, "disclosure_to_patch": {"available": false, "missing": ["end"]}, "time_unpatched": {"available": true, "seconds": 24937.177164, "hours": 6.926993656666667, "days": 0.28862473569444447, "min_seconds": 24937.177164, "max_seconds": 24937.177164, "approximate": false, "ongoing": true, "order_known": true, "batch_listing": false, "end_before_start": false, "start": {"timestamp": "2026-11-07T14:08:47.735Z", "date_only": false, "value": "2026-11-07T14:08:47.735Z", "kind": "milestone", "label": "Published", "source": "cvelistv5", "record": "CVE-2026-99281", "field": "cveMetadata.datePublished", "metric_role": "disclosure", "metric_basis": "recorded_event"}, "end": {"timestamp": "2026-11-07T21:04:24.912Z", "date_only": false, "label": "As of", "source": "Calculation clock"}}, "exploitation_to_patch": {"available": false, "missing": ["start"]}, "exploit_publication_to_patch": {"available": false, "missing": ["start"]}}}